Skip to content

Conversation

smorimoto
Copy link
Member

This change minimises my concerns, which I tried to address in #354, in a different way as reasonably and acceptably as possible.

Signed-off-by: Sora Morimoto <[email protected]>
@smorimoto
Copy link
Member Author

@ljharb This change does not strictly enforce the npm version, but the narrow lower bound of Node.js restricts the use of a wide range of bundled versions of npm in most scenarios.

@smorimoto smorimoto mentioned this pull request Nov 10, 2023
Copy link
Member

@jasonwilliams jasonwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is much more preferential to introducing corepack. @smorimoto can I ask the context behind this? Did something break compatibility somewhere?

@smorimoto
Copy link
Member Author

@jasonwilliams Some people have experienced lockfile versions being rolled back to the old one due to the old npm version. (and I received some PMs about that 🤷‍♂️)

@smorimoto smorimoto merged commit 174b3d8 into main Nov 10, 2023
@smorimoto smorimoto deleted the bump-engines-node branch November 10, 2023 14:35
@ljharb
Copy link
Member

ljharb commented Nov 10, 2023

Totally agree.

You can also set engines.npm if strictly necessary.

@ljharb
Copy link
Member

ljharb commented Nov 10, 2023

and, you can specify lockfileVersion in npmrc.

@smorimoto
Copy link
Member Author

smorimoto commented Nov 10, 2023

and, you can specify lockfileVersion in npmrc.

Oh, I didn't know about that. I don't really use npm these days, but it seems to be okay to use it recently.

@smorimoto
Copy link
Member Author

@ljharb Thank you for the great review to get things moving in a right direction!

@ljharb
Copy link
Member

ljharb commented Nov 10, 2023

It remains as it's always been, the best choice :-)

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

Successfully merging this pull request may close these issues.

3 participants