-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng xi18n fails with Node 12.0 (FIXED with Node.js 12.1+) #14351
Comments
Even though this issue isn't about something broken in the CLI, a lot of users will run into it now that node 12 is out and so we should leave it pinned for a while. |
bugs all around in 12 :( angular/angular-cli#14351 angular/angular-cli#14357 angular/angular-cli#14339 google pls
This should now be corrected in Node.js 12.1.0 or greater (changelog). |
Closing as fixed by Node 12.1 |
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. |
🐞 Bug report
Is this a regression?
Yes it was working in node <12
Description
With Node 12.0.0 export i18n isn't working, due to this issue nodejs/node#27379 on nodejs side
🔬 Minimal Reproduction
Run
ng xi18n --i18n-format=xmb --output-path locale
🔥 Exception or Error
🌍 Your Environment
Angular CLI: 8.0.0-rc.2
Node: 12.0.0
OS: win32 x64
Angular: 8.0.0-rc.2
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker
Package Version
@angular-devkit/architect 0.800.0-rc.2
@angular-devkit/build-angular 0.800.0-rc.2
@angular-devkit/build-optimizer 0.800.0-rc.2
@angular-devkit/build-webpack 0.800.0-rc.2
@angular-devkit/core 8.0.0-rc.2
@angular-devkit/schematics 8.0.0-rc.2
@angular/cdk 8.0.0-rc.0
@angular/http 8.0.0-beta.10
@angular/material 8.0.0-rc.0
@angular/pwa 0.800.0-rc.2
@ngtools/webpack 8.0.0-rc.2
@schematics/angular 8.0.0-rc.2
@schematics/update 0.800.0-rc.2
rxjs 6.5.1
typescript 3.4.5
webpack 4.30.0
Anything else relevant?
It is fixed in NodeJS v.12.1.0 in this PR
cc @filipesilva
The text was updated successfully, but these errors were encountered: