Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

Node dependency version fix. #44

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Node dependency version fix. #44

wants to merge 1 commit into from

Conversation

aryannarora
Copy link

@aryannarora aryannarora commented Mar 15, 2018

@bkeepers , Version "^8.0" are all supported. Initial ones requires --harmony flag for rest/spread operator. Source here. However, using "^8.0" throws the same error as present, "8.x" works just fine.

@zeke
Copy link
Contributor

zeke commented Mar 16, 2018

using "^8.0" throws the same error as present

What is the error? Maybe it needs to be ^8.0.0?

@aryannarora
Copy link
Author

Hii @zeke. This PR is about the error that Glitch throws i.e Node.js version >=7.7 is required. You have v6.13.1. on specifying node version ^8.0 or ^8.0.0 in package.json. I tried to use other versions like ^8.3.0 or something but it doesn't seem to work. So far, 8.x works fine. :)

@bkeepers
Copy link
Contributor

@aryannarora sorry, I merged #46 before I saw that this was open. Can you check that it works for you?

@aryannarora
Copy link
Author

@bkeepers No worries. :)
I tried to use node: ">=8.3.0" but Glitch gives the same error. 😢
It only works when we specify a more exact version like "8.x" or say "9.x". Anything else gives a Couldn't found node error. 😕

@zeke
Copy link
Contributor

zeke commented Mar 17, 2018

Trying to figure out why Glitch doesn't support all semver-compliant ranges: https://twitter.com/zeke/status/974723218064855040

Twitter
“@_gw can you take a peek at this `engines.node` question? https://t.co/RJBmkCmgbK”

@aryannarora
Copy link
Author

@zeke Please tell me if you find the reason. :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants