can you do a release?

With npm 7 being default, npm install command fails on apps that use typescript 4 because latest version of tsickle has a peerDependency of typescript 3. It was changed to typescript 4 on https://github.com/angular/tsickle/pull/1213, but it isn’t released.

While it’s possible to use --force or --legacy-peer-deps params on npm install to workaround the problem, would be good if the package could be released.

[brad4d]

At this point I think it’s clear that we aren’t going to do any more releases.

[rohitpratapitm]

Still facing the same issue while creating a new application using angular cli and npm v7.15.1

@angular/cli 11.2.x // has a peerDependency of typescript <4.1 @tsickle 0.39.1 // has a peerDependency of typescript ~3.8.2

Same issue with tsickle v 0.40.0 as well. There the peer Dependency is typescript ~4.2

Since npm v7 installs peer dependencies automatically, it is getting into version conflict issue. See error below:

> npm "install"

(node:15608) ExperimentalWarning: The fs.promises API is experimental
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: delete-me-app@0.0.0
npm ERR! Found: typescript@4.1.5
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"~4.1.5" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"~3.8.2" from tsickle@0.39.0
npm ERR! node_modules/tsickle
npm ERR!   dev tsickle@"0.39.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.