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

Incompatiable with Node v10 #31

Open
mririgoyen opened this issue May 5, 2018 · 5 comments
Open

Incompatiable with Node v10 #31

mririgoyen opened this issue May 5, 2018 · 5 comments

Comments

@mririgoyen
Copy link

When installing this module, the following error is returned.

error s3-streams@0.3.0: The engine "node" is incompatible with this module. Expected version "^1.2.0".

If installed with the --ignore-engines flag, it works without issue. Please relax your node engines restrictions in the package.json file.

@andylockran
Copy link

@goyney This looks like it'll now work, based on the CI reporting that nodeV10 is now supported. Please let us know.

@adi87
Copy link

adi87 commented Jan 24, 2019

Hi there! It looks like I'm still getting this error with yarn while trying to install v0.4.0

error s3-streams@0.4.0: The engine "node" is incompatible with this module. Expected version "^1.2.0". Got "10.13.0"

@andylockran
Copy link

andylockran commented Jan 29, 2019 via email

@hilkeheremans
Copy link

@andylockran The yarn issue mentioned above is just the engines field in package.json holding an ancient config. See the third commit in #24 (c874b86) to resolve that issue, but the PR as a whole is probably out of date, so you may want to manually adjust the field instead and close that PR.

@indiejames
Copy link

Any chance this ancient issue gets resolved?

donpedro added a commit to gulpetl/s3-streams that referenced this issue 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

No branches or pull requests

5 participants