[BUG] [typescript-angular] unable to run npm install after generating client

[libliflin]

Hi,

Please confirm tsickle version aligns with typescript version in most updated maven central jar. Currently they do not align (~4.3 and >=4.4.0 respectively) and npm install requires --force.

Suggested fix: remove tsickle from requirements for generated typescript code.

[iErKy]

Hello,
I've got same problem here, tsickle has compatibility problems with most recent typescript version (>=4.4.0), answer for this issues on angular/tsickle is avoid using it unless you really need it.

#angular/tsickle#1322

Suggested fix: remove tsickle

[ddurham2]

I had to remove tsickle from the generated package's devDependencies as well. The latest tsickle (0.46) release doesn't even install.

[wing328]

@ddurham2 thanks for sharing a fix. Can you please file a PR with the suggested fix when you've time?

[ddurham2]

same as #11233 and #12483

[ddurham2]

oh, I just run
sed -e 's/.*tsickle.*//' -i package.json
as part of my pipeline before installing/building/publishing,,,

And so, as far as I know, the fix is to just remove tsickle from package.json here

I'm not entirely sure what tsickle is useful for. Their page itself says it's experimental.

Being in the devDependences, it's not entirely necessary for deployed apps.

[kyryl-bogach]

The issue is still present

[blaghed]

Can confirm this is still happening on v6.2.1 (current master).
I'm able to fix this by having my own template "package.mustache" without the "tsickle" dependency, but would love for a fix at source.
Do you need someone to contribute this 1 line removal?

[M-a-c-Carter]

@blaghed I was building fine without it.
also its not really something that should be used apparently
angular/tsickle#1429

[M-a-c-Carter]

and for that matter @ddurham2 's solution is valid, but there should be an update to this project.