Skip to content
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

Leverage Node 22.3.0's node --run for run-s when possible. #155

Open
jdalton opened this issue Oct 3, 2024 · 2 comments
Open

Leverage Node 22.3.0's node --run for run-s when possible. #155

jdalton opened this issue Oct 3, 2024 · 2 comments

Comments

@jdalton
Copy link

jdalton commented Oct 3, 2024

semver.satisfies(process.versions.node, '>=22.3.0')

There could even be a separate node-s for the https://nodejs.org/api/cli.html#--run command. It does have limitations though so making it a separate command that falls back to a more run-s kind of command would be nice. The speed up is very nice.

@voxpelli
Copy link
Collaborator

voxpelli commented Oct 3, 2024

The differences between pnpm, yarn, npm are already challenging – this feels a bit like one more standard 😂

That said, it could be a benefit that it has less features

(Someone should do a write up of the differences between them all so that we could ideally arrive at a standard for npm scripts with maybe two levels "lightweight" runner like node --run and "full featured" like the others, and ensure that the full featured ones are compatible with each other and a strict superset of the lightweight one and as such also compatible with it)

@bcomnes
Copy link
Owner

bcomnes commented Oct 3, 2024

I would be nervous to default to it initially, but maybe we could flag it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants