Repository navigation
Closed
angular/angular-cli
#7702Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimearea: i18nIssues related to localization and internationalizationIssues related to localization and internationalizationregressionIndicates than the issue relates to something that worked in a previous versionIndicates than the issue relates to something that worked in a previous version
Description
I'm submitting a...
[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
Using Angular CLI's ng xi18n command will extract messages from Angular 4.x to 5.0.0-beta.6 but not on 5.0.0-beta.7.
Expected behavior
Message extraction should work using beta.7.
Minimal reproduction of the problem with instructions
ng new test-proj
cd test-proj
ng generate component i18n-test
echo "<p i18n>Hello world</p>" > ./src/app/i18n-test/i18n-test.component.html
npm run ng -- xi18n
stat src/messages.xlf # file exists
rm src/messages.xlf
# update to beta.6
npm i @angular/{animations,common,compiler,core,forms,http,platform-browser,platform-browser-dynamic,router,compiler-cli,language-service}@5.0.0-beta.6 typescript@2.5.1
npm run ng -- xi18n
stat src/messages.xlf # file exists
rm src/messages.xlf
# update to beta.7
npm i @angular/{animations,common,compiler,core,forms,http,platform-browser,platform-browser-dynamic,router,compiler-cli,language-service}@5.0.0-beta.7 typescript@2.5.1
npm run ng -- xi18n
stat src/messages.xlf # file does not exist
What is the motivation / use case for changing the behavior?
Environment
Angular version: 5.0.0-beta.7
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: v6.11.1
- Platform: Windows
Others:
/cc @ocombe
Metadata
Metadata
Assignees
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimearea: i18nIssues related to localization and internationalizationIssues related to localization and internationalizationregressionIndicates than the issue relates to something that worked in a previous versionIndicates than the issue relates to something that worked in a previous version
Activity
vicb commentedon Sep 15, 2017
@ocombe ypu might want to discuss it with @matsko - I think he changed the extraction
fix(@ngtools/webpack): use outDir for i18n extraction in Angular v5
ocombe commentedon Sep 15, 2017
This is because genDir has been replaced by outDir in the new pipeline. I've created a fix for the cli.
fix(@ngtools/webpack): use `outDir` for i18n extraction in Angular v5
fix(@ngtools/webpack): use `outDir` for i18n extraction in Angular v5
fix(@ngtools/webpack): use `outDir` for i18n extraction in Angular v5
fix(@ngtools/webpack): use `outDir` for i18n extraction in Angular v5
angular-automatic-lock-bot commentedon Sep 12, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
fix(@ngtools/webpack): use `outDir` for i18n extraction in Angular v5