-
-
Notifications
You must be signed in to change notification settings - Fork 208
-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support node --run
#210
Labels
enhancement
New feature or request
Comments
PR welcome - tho I don't know if there is way we could detect that |
@antfu I would assume that first checking if Node >= 22. After that, maybe ask users if they prefer to use whatever package manager they use, or node --run. If they use npm, I would turn it on by default |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Clear and concise description of the problem
Node 22 introduced the
--run
flag, which allows it to run scripts in the same way npm, pnpm, yarn and bun do. It'd be nice to support this, since it seems to be significantly fasterSuggested solution
Add
node --run
to the list of options that thenr
command can useAlternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: