-
Notifications
You must be signed in to change notification settings - Fork 25.3k
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
Angular 9.0.3 ngcc fails to process ng2-dragula #35709
Comments
Same for me with the package @ngx-translate/http-loader
|
I have an error |
I am having same error while trying to build my angular library Package.json "@angular/animations": "^9.0.3",
"@angular/cdk": "^9.1.0",
"@angular/common": "^9.0.3",
"@angular/compiler": "^9.0.3",
"@angular/core": "^9.0.3",
"@angular/forms": "^9.0.3",
"@angular/platform-browser": "^9.0.3",
"@angular/platform-browser-dynamic": "^9.0.3",
"@angular/router": "^9.0.3", Error Log
|
I am also getting this error since upgrading to Angular 9.0.3 |
I had trouble with ngcc when compiling
I don't know if you guys will have success with this, but the issue went away when deleting |
I'm using the latest version of Angular 9.0.3 with Ionic and I'm also getting an error: D:_GIT\AppMobile>ionic serve
[INFO] Development server running!
[INFO] Browser window opened to http://localhost:8100! |
Looks related to #35132 |
Yes I agree. Looking for a fix now. |
In the case of
|
But the |
What's a good short term fix for the people who are updating from 7.1 to 9.0.x at this time? |
@rohanahata - fix on 9.0.2 until 9.0.4 is released. |
The following is my package.json. Which ones do I change to 9.0.2 to downgrade?
|
At a minimum you need to change |
If a package has a source-map but it does not provide the actual content of the sources, then the source-map flattening was crashing. Now we ignore such mappings that have no source since we are not able to compute the merged mapping if there is no source file. Fixes angular#35709
If a package has a source-map but it does not provide the actual content of the sources, then the source-map flattening was crashing. Now we ignore such mappings that have no source since we are not able to compute the merged mapping if there is no source file. Fixes angular#35709
So I have a fix for the
It seems that there is a mapping to a line that doesn't actually exist in the original source content. |
@petebacondarwin I found that I could get past some issues in packages by removing node_modules and re-running |
I had same error and tried many different solution. Finally I've solved it with adding following lines to
Basically, it will be solved when you disable the "Ivy" on angularCompilerOptions. |
The proper solution was given above. Liking your own advice doesn't increase its weight. Disabling Ivy is not the way to go. Just downgrade the Angular Version to yesterday's. |
For me, even using version 9.0.2 I still get the error : Am I missing something? What can I provide that might be useful? |
@GitHubish Remove the node_modules folder & your package manager's lock file and finally run the |
Here it works after deleting node_modules and running npm i again. I'm using angular 9.0.3 |
@Ploppy3 same thing
|
@GitHubish - did you change the package.json dependencies to 9.0.2 before removing |
Also fails on ngx-loading-bar@4.2.0, using @angular/compiler-cli@9.0.3. All fine using 9.0.2. |
This seems like a pretty bad regression to wait this long, unless 'revert to old version' is acceptable. *edit - thanks for the quick turnaround ng team :) |
If a package has a source-map but it does not provide the actual content of the sources, then the source-map flattening was crashing. Now we ignore such mappings that have no source since we are not able to compute the merged mapping if there is no source file. Fixes angular#35709
…-maps Previously when rendering flattened source-maps, it was assumed that no mapping would come from a line that is outside the lines of the actual source content. It turns out this is not a valid assumption. Now the code that renders flattened source-maps will handle such mappings, with the additional benefit that the rendered source-map will only contain mapping lines up to the last mapping, rather than a mapping line for every content line. Fixes angular#35709
@tomgruszowski - we hear you. The PR is just about green and should be merged in the next hour. The plan is to then roll out a new patch release. So you should be unblocked before the end of the day. Sorry that this release caused some issues and frustration. |
…-maps (#35718) Previously when rendering flattened source-maps, it was assumed that no mapping would come from a line that is outside the lines of the actual source content. It turns out this is not a valid assumption. Now the code that renders flattened source-maps will handle such mappings, with the additional benefit that the rendered source-map will only contain mapping lines up to the last mapping, rather than a mapping line for every content line. Fixes #35709 PR Close #35718
…-maps (#35718) Previously when rendering flattened source-maps, it was assumed that no mapping would come from a line that is outside the lines of the actual source content. It turns out this is not a valid assumption. Now the code that renders flattened source-maps will handle such mappings, with the additional benefit that the rendered source-map will only contain mapping lines up to the last mapping, rather than a mapping line for every content line. Fixes #35709 PR Close #35718
Angular 9.0.4 has been released which should fix these problems. |
Nope it didn't... worse happened for me after updating to 9.0.4 from 9.0.2.. had to rollback my package* files and had to delete node_modules and run |
@petebacondarwin Just so you know, your commits does fix my issue. |
I'm receiving the same error with Here's my
Error:
|
@naveedahmed1 There has not been a hot-patch for the 9.1.0-next release line, it was only 9.0.4 that was released the same week as 9.0.3. There will be a 9.1.0-next release around Wednesday/Thursday this week that should address the crash. |
Thank you so much @JoostK for the update. |
I fixed downgrade to 9.0.4 release. The 9.1.0 versión hava a lot of bugs yet. |
Maybe this comment angular/angular-cli#17115 (comment) relates to current issue too. |
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. |
🐞 bug report
Affected Package
@angular/compiler-cli
Is this a regression?
Yes it works properly with angular 9.0.2
Description
ngcc build failed with ng2-dragula.
🔬 Minimal Reproduction
npm install
npm run build ngcc-ng2-dragula-bug-demo
🔥 Exception or Error
🌍 Your Environment
Angular Version:
Anything else relevant?
I guess the error is caused by commit df816c9 which is related to sourcemap processing, so ng2-dragula's sourcemap may have some problems.
The text was updated successfully, but these errors were encountered: