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

Fix #759 Drop support for Node 12 #763

Merged
merged 6 commits into from
Feb 20, 2023

Conversation

FluorescentHallucinogen
Copy link
Contributor

No description provided.

@andreban
Copy link
Member

@FluorescentHallucinogen
Copy link
Contributor Author

@andreban We are increasing the minimum supported Node.js version only because of the lerna dev dependency in the root project. But cli, core and validator packages don't use lerna (directly). I mean that output npm packages still can work in Node.js 12.

Should we update /packages/cli/README.md and /packages/core/README.md at all?

Should we add "engines": { "node": ">=14.15.0" } to /packages/cli/package.json and /packages/core/package.json?

Should we update https://github.com/GoogleChromeLabs/bubblewrap/blob/main/packages/cli/src/lib/Cli.ts#L39-L42?

@andreban
Copy link
Member

By dropping support to Node 12 we'll stop testing the code against it and ensuring using APIs that work on Node 12. Right now, the whole application will still be compatible but, over time, it's likely that it will stop working on Node 12. I'd rather clarify this to users in documentation / code now, rather than surprise people when it breaks.

@andreban
Copy link
Member

@FluorescentHallucinogen
Copy link
Contributor Author

@andreban BTW, what about the validator package? I see that core and cli packages was updated to v1.19.1, but the validator is still v1.18.1. 🤔

@FluorescentHallucinogen
Copy link
Contributor Author

@andreban And unfortunately you have not answered the question, should we add "engines": { "node": ">=14.15.0" } to /packages/cli/package.json and /packages/core/package.json? And what about /packages/validator/package.json?

If so, should we also create an .npmrc file with engine-strict=true? Without this flag, the engines field in package.json is advisory only and will only produce warnings when the package is installed as a dependency.

Copy link
Member

@andreban andreban left a comment

Choose a reason for hiding this comment

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

LGTM, Thank you!

@andreban andreban merged commit 88b2cb0 into GoogleChromeLabs:main Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants