-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
[JS problem introduced with ?.] #49
Comments
We are also running into the same issue. All the deployments till 4 hours ago were successful. After that, all have failed. |
Hello, This is related to the node engine version required. Look the engines.node version in the package.json it requires node version 14.6.0 or above to run. @arafesthain @saakshig @engineerakki could you update node and see if you still have issue please ? |
@scolladon yep I saw this in review process but don't understand why installation of sgd is not failing if I'm missing node version requirement |
@scolladon alright from there (for custom labels too) 👍 |
Maybe because you did an update instead of an install ? Would you be able to suggest a process for the next time ? So upgrading the engine to benefit from the new feature of the js will not make you lose time because of breaking in runtime. |
@scolladon truth is my pipeline didn't break without updating node version :') but on my (wonderful) windows computer it did.. For this kind of stuff I will suggest a major release ? but not sure it fit in this scenario. I did force the pipeline to stay on a chosen version so it will well fit in my case ^^ |
Good advice thanks We will definitly need to deal properly with this kind of situation @mehdisfdc I was a little bit rough on this one :D |
Anything that I should have done in version 3.3.1 ?
Execution context
Operating System: …
Windows 10
NPM version: …
6.14.5
Node version: …
v13.12.0
sgd version: …
3.3.1
The text was updated successfully, but these errors were encountered: