Angular dev-server (NX) builder, not usable with NX 18 and Angular < 16 about nx HOT 7 CLOSED

@AronHoxha there's a legit issue for which I created a PR, but note that Angular versions lower than 15 are not supported. From the failure logs you shared, you seem to be using Angular 13.3.11, which is not a supported version.

from nx.

esbuild was introduced in angular 16 and the flag you're trying to use in 16.1, there's nothing NX can do about that. Upgrade your angular version.

You should always upgrade nx with nx migrate <version>, this will upgrade and migrate angular with it. https://nx.dev/features/automate-updating-dependencies

Here's the version matrix: https://nx.dev/nx-api/angular/documents/angular-nx-version-matrix

from nx.

esbuild was introduced in angular 16 and the flag you're trying to use in 16.1, there's nothing NX can do about that. Upgrade your angular version.

As it is in our project we can't migrate the angular version as of right now.

We don't want to use esBuild for our dev-server, but it's impossible to use the dev-server even with foreceEsbuild: false since it still fails.

Can't the default value of forceEsbuild be undefined, so that nx is compatible angular versions <16?

Thank you for sharing the compatibility matrix!

from nx.

esbuild was introduced in angular 16 and the flag you're trying to use in 16.1, there's nothing NX can do about that. Upgrade your angular version.

As it is in our project we can't migrate the angular version as of right now.

We don't want to use esBuild for our dev-server, but it's impossible to use the dev-server even with foreceEsbuild: false since it still fails.

Can't the default value of forceEsbuild be undefined, so that nx is compatible angular versions <16?

Thank you for sharing the compatibility matrix!

What happens if you do not specify forceEsbuild in your conf at all?

from nx.

What happens if you do not specify forceEsbuild in your conf at all?

The same error

from nx.

What happens if you do not specify forceEsbuild in your conf at all?

Note: manually remove the following line from node_modules, successfully serves the app. Not sure if it breaks using NX with higher versions of angular

from nx.

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.

from nx.