-
Notifications
You must be signed in to change notification settings - Fork 12k
Angular Cli Errors with nodejs 5.5.0 #4604
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
Comments
OBVIOUSLY, the best solution would be to update to the supported Node 6.9 but in my case, it was out of my hand The solution that fixed those issues for me on node 5.5.0 was npm shrinkwrap here is the solution rm -rf node_modules #remove all installed modules
npm install #install al modules back
npm remove @ngtools/webpack
npm install @ngtools/[email protected] # install the specific version that works with node 5.5.0
npm remove @ngtools/json-schema
npm install @ngtools/[email protected] # install the specific version that works with node 5.5.0
npm shrinkwrap --dev #if it throws errors about extraneous dependencies, use npm prune
a new npm-shrinkwrap.json file is generated and will guarantee that you get the specified versions above read more about srinkwrap here |
+1 |
We do not support Node version before 6.9. The Beta 28.3 was the last version to support Node 4 and 5. |
@hansl from the CHANGELOG.md for beta 28:
I saw the warning, but there was NO error that told me that you don't support Node version before 6.9. according to above, I expected an error that breaks the build and mentions that it wont work because of node version... |
So, this error is happening in my build server and local machine, both with node 5.5. My app it's using the version beta-19 of angular-cli, and updating my local machine and my build server to node 6.9.5, everything is working fine... |
Our build server also fails with beta.28.3, probably [email protected] and [email protected] are not locked and install more recent version automatically on build that go through npm install steps. I would still see this as an issue, if beta.28.3 is the last version which should work on node 5... We will ask admins to update the node version on the build server, but I completely understand that sometimes it's not possible. |
Hi, Isn't this line making angular cli installable even if node version is not supported ? ("node": ">= 6.9.0",) ref: angular#4604
Hi, Isn't this line making angular cli installable even if node version is not supported ? ("node": ">= 6.9.0",) ref: #4604
Hi, Isn't this line making angular cli installable even if node version is not supported ? ("node": ">= 6.9.0",) ref: angular#4604
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
Versions.
Repro steps.
The log given by the failure.
Also this:
Mention any other details that might be useful.
Yesterday
@ngtools/[email protected]
was updated to1.0.3
and also@ngtools/[email protected]
was updated to1.2.9
Seems like those two updates introduces ES2016 syntax that Node 5.5.0 does not like.
I know angular cli team did their due diligence and mentioned that node < 6.9 will no longer be supported... BUT, it would have been nice if you could at least pin the versions
Those two releases mentioned above, should have been minor releases.
Additionally, @angular/[email protected] should have had the following dependencies:
"@ngtools/json-schema":"1.0.x"
instead of"^1.0.0"
and
"@ngtools/webpack":"1.2.x"
instead of"^1.2.3"
I appreciate all the hard work from angular team. I am not aware of your development process but s an outsider, that's what I think.
I found a solution to this, please find it it in the comments
The text was updated successfully, but these errors were encountered: