Error extracting i18n tags with Angular 15+

[jaudette790]

Error extracting i18n tags with Angular 15+

[mattlewis92]

One temporary workaround that I found is to delete the sourcemap before extracting i18n:

rm node_modules/angular-calendar/fesm2020/angular-calendar.mjs.map

[mattlewis92]

I've filed an issue on the angular CLI repo with steps to reproduce, hopefully they can find a proper fix soon 🙏

angular/angular-cli#25413

[cmayankc]

+1

[DerZyklop]

Have the same on Angular 15. @jaudette790 you could change 'Angular 16' to 'Angular 15+' in the title.

[kukjevov]

@jaudette790 can you verify whether babel version 7.22.7 solves issue also for you?

angular/angular-cli#25414 (comment)

[mattlewis92]

Verified that the issue is fixed in angular CLI 16.1.4!

[matts-bot]

Thanks so much for opening an issue! If you'd like to support this project, then please consider sponsoring me

[geraldspreer]

I can confirm this issue. Exactly like it was described by @jaudette790. I would be really cool @mattlewis92 if you would be able to fix this.

[geraldspreer]

The error is thrown by babel.js https://unpkg.com/@babel/[email protected]/babel.js.map

const COL_GTR_EQ_ZERO = 'column must be greater than or equal to 0 (columns start at column 0)';

[DerZyklop]

And i confirm @geraldspreer. Error is

Error: /Users/nils/S/plano/scheduler.frontend.ng2/node_modules/angular-calendar/fesm2020/angular-calendar.mjs: `column` must be greater than or equal to 0

[jaudette790]

Have the same on Angular 15. @jaudette790 you could change 'Angular 16' to 'Angular 15+' in the title.

I updated the title, but I did not get the error until I updated to Angular 16

[mattlewis92]

Hey folks, I just took a quick look at this issue and this seems like a bug with angular rather than anything I'm able to fix my end. You can see there are other people running into the problem and that aren't using this package.

For example:

• angular/angular-cli#25403
• angular/angular-cli#25414

[geraldspreer]

Thank you @mattlewis92 for providing this info to temporary fix this problem.

[kukjevov]

It is a problem of Babel which is already under resolution, but not closed yet babel/babel#15712