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

252 remove engines from package.json #253

Merged
merged 1 commit into from Jun 14, 2020

Conversation

cjpatoilo
Copy link
Member

@cjpatoilo cjpatoilo commented Jun 12, 2020

This Pull Request should close the issue #252

Description

Consumers of the npm package just get the dist files so they aren't affected by this AFAICT. What Milligram uses to build and develop itself does shouldn't affect consumers. So having a Node.js version could be considered wrong.

This will allow Milligram to use whatever Node.js version we want to use without having to support unsupported Node.js versions anymore.

Maybe in the future make sense Milligram to use only the up to date versions of the Node.js (>=lts) but for now, the engines property should be removed from package.json

Hightlight

  • remove the engines property from package.json (8c80c8f)

@cjpatoilo cjpatoilo self-assigned this Jun 12, 2020
@cjpatoilo
Copy link
Member Author

@westtrade @davidroeca please, can you review this pull request

@cjpatoilo cjpatoilo changed the title 252 remove engine from package.json 252 remove engines from package.json Jun 12, 2020
@davidroeca
Copy link

👍 looks good to me!

@cjpatoilo cjpatoilo merged commit 34569df into master Jun 14, 2020
@cjpatoilo cjpatoilo deleted the feature/252-remove-engine-from-package-json branch June 14, 2020 18:18
@GreatWizard
Copy link

Is it possible to release a new version with the fix of node engine?

@cjpatoilo
Copy link
Member Author

@GreatWizard I will prepare the new version ASAP #254

@cjpatoilo
Copy link
Member Author

@GreatWizard
Copy link

Thank you!

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.

None yet

3 participants