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

Package engine "Node >= 10.0.0" causing installation problem in Node 15.4.0 #452

Open
blfunex opened this issue Mar 3, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@blfunex
Copy link

blfunex commented Mar 3, 2021

Describe the bug
Can not install with node 15.4.0 using yarn.

To Reproduce

Get node 15.4.0, install yarn 1.22.5, then

$ yarn add nes.css

Expected behavior
NES.css installs correctly

Screenshots
image

Environment:

  • OS: Windows
  • Browser: N/A (not a concern)
  • Build environment (i.e. NodeJS): N/A (not building)

Suggestion(s) for fixing this issue
Remove the engine field from package.json, or update it.

Additional context
IDK, thanks.

@guastallaigor guastallaigor added the bug Something isn't working label Mar 5, 2021
@lukbukkit
Copy link
Contributor

This problem has already been fixed by #418 but has yet to be published. It would be nice if a new version could be released on NPM.

@gabrielgaraujo
Copy link

gabrielgaraujo commented Apr 4, 2021

This problem has already been fixed by #418 but has yet to be published. It would be nice if a new version could be released on NPM.

@lukbukkit How can I yarn add using the develop branch?

UPDATE
I've sorted it out, since I'm using it only for a local prototype I've used yarn link

Steps to set it up locally:

git clone [email protected]:nostalgic-css/NES.css.git && cd NES.css
cd <path-to-your-project> && yarn link nes.css     

@lukbukkit
Copy link
Contributor

Sorry for the late answer. I'm using yarn install --ignore-engines to install the dependencies for my project. To add the package you can edit the package.json file by hand.

@good-praxis
Copy link

#469 depicts the same issue. If it's fixed upstream, what does it take to get it into a release? This is a pretty breaking bug after all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants