question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Extraction stopped working after Angular upgrade 12 -> 13

See original GitHub issue
> ng run pt-client:xliffmerge

An unhandled exception occurred: NOT SUPPORTED: keyword "id", use "$id" for schema ID
See "/private/var/folders/q7/665kbmk952b7b_1dr7hyxybcwwrrp9/T/ng-9gMGfZ/angular-errors.log" for further details.
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! pt-client@0.0.6 tool:i18n:merge: `ng run pt-client:xliffmerge`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the pt-client@0.0.6 tool:i18n:merge script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/bernhard.behrendt/.npm/_logs/2021-11-04T15_05_50_035Z-debug.log

I’ve actually tried to solve in Pull Request #196 which break actually on jasmine test part

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:15
  • Comments:17

github_iconTop GitHub Comments

27reactions
daniel-sccommented, Feb 1, 2022

I created a xliff merge tool that nicely integrates with Angular CLI and (probably) caters most needs of former users of this tooling: https://github.com/daniel-sc/ng-extract-i18n-merge Feedback welcome! 😃

4reactions
wallace41290commented, Jan 19, 2022

+1 for a maintained fork or a native solution, merging xliff’s is essential!

Read more comments on GitHub >

github_iconTop Results From Across the Web

help(Upgrade): Unable to finish upgrade from 12 to 13 due to ...
When upgrading from angular 12 to angular 13 of the material library the upgrade completes successfully but the build fails with cryptic ...
Read more >
Angular migration from 12 to 13 getting error - Stack Overflow
I deleted package-lock.json, deleted the node_modules folder and did npm install and it fixed the issue.
Read more >
Guide to update your Angular application v11.0 -> v13.0 for ...
Run ng update @angular/core@13 @angular/cli@13 which should bring you to version 13 of Angular. You can now disable the navigation of a routerLink...
Read more >
What's new in Angular CLI 12.0? - Ninja Squad
The CLI now uses Webpack v5 under the hood . There is nothing to do to enjoy it: just update your application to...
Read more >
Angular Version Upgrade: A quick guide to upgrade from 9.0 ...
1. Perform an upgrade to angular's core and cli modules to version12.0 from the current version. The --force switch at the end is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found