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

updates package.json:engines to solve yarn's spurious warning message #24

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

sramam
Copy link

@sramam sramam commented May 4, 2017

Per yarnpkg/yarn#812, updates the engines parameters in package.json to resolve #21.

Wonder if these values actually need to be overhauled all together? Unsure of the usage profile, so leaving it alone for the moment.

@sammarks
Copy link

sammarks commented Jun 9, 2017

@izaakschroeder chances we can get this merged with a new release? This is currently preventing us from switching to yarn as it throws the error without using the --ignore-engines flag.

snyk-bot and others added 4 commits February 15, 2018 01:04
The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/npm:lodash:20180130

Latest report for sramam/s3-streams:
https://snyk.io/test/github/sramam/s3-streams
[Snyk Update] New fixes for 1 vulnerable dependency path
donpedro added a commit to gulpetl/s3-streams that referenced this pull request Aug 14, 2024
- fix tests under windows using [cross-env](https://www.npmjs.com/package/cross-env), and also this [problem + solution](https://stackoverflow.com/a/41236179/5578474)
- address ["engines" problem](izaakschroeder#24, izaakschroeder#31) by relaxing restrictions on nodejs versions
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.

Bogus warning with latest NodeJS
4 participants