-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Angular 16.1.1 causing problem with babel during compilation #25414
Comments
Well it looks like error which is some kind of combination with babel or something about source maps during transformation i also reported issue on babel, but i tried to "downgrade" babel and it still did not work. |
This comment was marked as spam.
This comment was marked as spam.
1 similar comment
+1 |
It is working, it was fixed by set these as
@alan-agius4 is it possible to set this version also for |
This fixes and issue with negative source maps columns Closes angular#25414
This fixes and issue with negative source maps columns Closes angular#25414
This fixes and issue with negative source maps columns Closes #25414
Closed via #25500. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Which @angular/* package(s) are the source of the bug?
compiler-cli
Is this a regression?
Yes
Description
After updating to angular 16.1.1 application will not compile anymore. Previous version 16.0.4 works just fine.
Minimal reproduction for non working version
git clone https://github.com/kukjevov/ng-universal-demo
cd ng-universal-demo
git checkout 2.0
npm install --legacy-peer-deps
npm run build
Minimal reproduction for working version
git clone https://github.com/kukjevov/ng-universal-demo
cd ng-universal-demo
git checkout 1.0
npm install --legacy-peer-deps
npm run build
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
The text was updated successfully, but these errors were encountered: