79423359

Date: 2025-02-08 14:40:18
Score: 1
Natty:
Report link

I ran into the same issue today, and I managed to fix it. Here’s what I did:

  1. I simply removed the node_modules folder and package-lock.json.

  2. I updated the @angular/localize package to version 19.1.5.

  3. I ran npm i.

  4. After that, I noticed that everywhere in the project where I had import {$localize} was highlighted in red.

  5. So, I removed all instances of import {$localize} from the files. It turned out that all the files containing import {$localize} were causing issues with i18n extraction. Surprisingly, everything worked fine after removing those imports.

I guess the maintainers of the library fixed the issue in this version.

Reasons:
  • Long answer (-0.5):
  • No code block (0.5):
  • Low reputation (1):
Posted by: FastNugget