moduleResolution bundler was not required before Angular v21

[muhamedkarajic]

Which @angular/* package(s) are the source of the bug?

compiler

Is this a regression?

Yes

Description

Image explains everything:

Is the old builder now depricated? Because my setup worked only with webpack not with esbuild? And I was not capable to set moduleResolution to builder ever. My current moduleResolution is set to 'node'.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run ng version)

Anything else?

No response

[JoostK]

This is independent of the builder in use; moduleResolution: node is deprecated from TypeScript's perspective and doesn't consider export maps, which is why the import of @angular/common/http no longer resolves.

Angular CLI 21 contains a migration that aims to set moduleResolution: bundler during ng update

[clydin]

Closing as per above.

[muhamedkarajic]

This is independent of the builder in use; moduleResolution: node is deprecated from TypeScript's perspective

@JoostK that must be then for typescript 6.0? In my package.json it was still "typescript": "~5.9.2" however? I'm confused who decided its now depricated based on what? Could you explain a bit more?

Was the http lib maybe generated for npm but with typescript v6.0.X? Should they not have supported still a release since they are officially on typescript 5.9.X. I would argue this is not closed @clydin

[JeanMeche]

Yeah it is a TS 6.0 deprecated: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/

But we required it as when we changed some of the package structure.

[JoostK]

It is indeed only 6.0 and up where it's deprecated, with it no longer implemented in TS7.

Regardless of TS's deprecation, node (aka node10) just does not support modern packaging approaches (i.e. export maps) and therefore won't be able to consume all packages that announce their entry-points specifically through package.json#exports.

[muhamedkarajic]

Okay thank you both very much @JeanMeche & @JoostK , guess I have no choice then to get esbuild now working.

[JoostK]

The webpack builder should still work fine with bundler module resolution.

[muhamedkarajic]

@JoostK could you maybe tell me, libs like "leaflet": "~1.9.4" are they not gonna work with typescript v6.0.X either?

E.g.

File X depends on 'leaflet'. CommonJS or AMD dependencies can cause optimization bailouts.
File X depends on 'lodash'. CommonJS or AMD dependencies can cause optimization bailouts.
File X depends on 'file-saver'. CommonJS or AMD dependencies can cause optimization bailouts.

[JoostK]

Those warnings have nothing to do with a resolution mode or TS compiler support; it's just that CJS has sub-optimal tree-shaking characteristics where tools are typically reluctant to optimize them to the same extent as for ESM, hence the CLI reporting a warning that using CJS libs may negatively affect optimization opportunities.