Closed ZissisT closed 3 months ago
Unfortunately, with esbuild, it is no longer possible to exclude certain dependencies from being processed. Additionally, all environments and browsers officially supported by Angular natively support the WHATWG URL Standard's URL API, rendering the use of this module redundant.
As described in the previous issue, this is quite trivial to fix at the library level and ensure compatibility with various processing and bundling methods: https://github.com/angular/angular-cli/issues/21735#issuecomment-915974013. Therefore, I recommend either reaching out to the library author or removing this module from your dependencies.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
Command
build, serve
Is this a regression?
The previous version in which this bug was not present was
Angular 16.x.x
Description
After Angular17 upgrade, esbuild is the default for new projects. In earlier versions that used webpack, this issue was solved with https://github.com/angular/angular-cli/pull/22629 (@dgp1130 , @alan-agius4 ). It had to do with excluding 'erroneous' modules that did not support downleveling, eg. whatwg-url. Now this exclusion list seems gone since esbuild uses different configuration. As a result app can not be loaded. Also mentioning that while using native federation as well which has a custom esbuilder I think, same thing happens.
Minimal Reproduction
Exception or Error
Your Environment
Anything else relevant?
No response