Skip to content

Upgrade Angular to v22 and TypeScript to v6 - #106

Open
JeevanMahesha wants to merge 3 commits into
stackblitz:mainfrom
JeevanMahesha:update-angular-v22
Open

Upgrade Angular to v22 and TypeScript to v6#106
JeevanMahesha wants to merge 3 commits into
stackblitz:mainfrom
JeevanMahesha:update-angular-v22

Conversation

@JeevanMahesha

Copy link
Copy Markdown
Contributor

This PR upgrades the Angular framework dependencies and CLI tools to version 22.0.0, updates TypeScript to v6.0.3, and configures specific compiler diagnostic options to suppress unnecessary nullish coalescing and optional chaining warnings in the Angular build.

@bolt-new-by-stackblitz

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@JeevanMahesha
JeevanMahesha marked this pull request as ready for review June 3, 2026 16:40
@JeevanMahesha

JeevanMahesha commented Jun 3, 2026

Copy link
Copy Markdown
Contributor Author

@SamVerschueren Test and package lock check are failing randomly.

… compiler options to suppress nullish/optional chain diagnostics
@msmallest

Copy link
Copy Markdown

I am not familiar with the tests that are failing, but I imagine it is either upstream or downstream of this current limitation: #105

@JeevanMahesha

Copy link
Copy Markdown
Contributor Author

@sulco can you review this PR.

@michael-small

michael-small commented Jul 30, 2026

Copy link
Copy Markdown

@JeevanMahesha thank you for this. By the way, 22.1 just came out today. Package versions from when I manually ng update @angular/core @angular/cli on an existing Stackblitz 21.1 starter https://stackblitz.com/edit/stackblitz-starters-awkyj8bd?file=package.json

edit: hmm, seems to be an error while running. All I did was do a standard update to the starter's Angular version.

Webcontainer issue? An Angular project configured like this otherwise locally works

Prebundling has been configured but will not be used because caching has been disabled.
[rolldown] Downloading @rolldown/binding-wasm32-wasi@1.1.5 on WebContainer...
Packages: +7
+++++++
Progress: resolved 7, reused 0, downloaded 7, added 7, done

dependencies:
+ @rolldown/binding-wasm32-wasi 1.1.5 (1.2.1 is available)

Full:

❯ npm install && npm start

added 355 packages in 3s

99 packages are looking for funding
  run `npm fund` for details

> start
> ng serve

Prebundling has been configured but will not be used because caching has been disabled.
[rolldown] Downloading @rolldown/binding-wasm32-wasi@1.1.5 on WebContainer...
Packages: +7
+++++++
Progress: resolved 7, reused 0, downloaded 7, added 7, done

dependencies:
+ @rolldown/binding-wasm32-wasi 1.1.5 (1.2.1 is available)

 WARN  Issues with peer dependencies found
.
└─┬ @rolldown/binding-wasm32-wasi 1.1.5
  └─┬ @napi-rs/wasm-runtime 1.2.0
    ├── ✕ unmet peer @emnapi/core@^2.0.0-alpha.3: found 1.11.1 in @rolldown/binding-wasm32-wasi
    └── ✕ unmet peer @emnapi/runtime@^2.0.0-alpha.3: found 1.11.1 in @rolldown/binding-wasm32-wasi

Done in 3.8s
An unhandled exception occurred: Cannot find native binding. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
See "/tmp/ng-oOxYu4/angular-errors.log" for further details.
(node:12) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

edit 2: After a couple hours, I re-opened the link, and the project servers despite throwing some warnings. Still strange, but nice it ends up working.

> start
> ng serve

Prebundling has been configured but will not be used because caching has been disabled.
[rolldown] Downloading @rolldown/binding-wasm32-wasi@1.1.5 on WebContainer...
Packages: +7
+++++++
Progress: resolved 7, reused 0, downloaded 7, added 7, done

dependencies:
+ @rolldown/binding-wasm32-wasi 1.1.5 (1.2.1 is available)

Done in 3.6s
(node:12) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

(node:12) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants