-
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
Angular 12 AngularWebpackPlugin is not compatible with some webpack plugins #21290
Closed
2 of 15 tasks
Labels
area: @ngtools/webpack
freq1: low
Only reported by a handful of users who observe it rarely
severity5: regression
type: bug/fix
Milestone
Comments
alan-agius4
added
action: cleanup
The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews
area: @ngtools/webpack
freq1: low
Only reported by a handful of users who observe it rarely
severity5: regression
type: bug/fix
labels
Jul 6, 2021
alan-agius4
removed
the
action: cleanup
The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews
label
Jul 6, 2021
clydin
added a commit
to clydin/angular-cli
that referenced
this issue
Jul 6, 2021
…sources The asset caching for Angular component resources previously required that all assets had an originating file. However, some Webpack plugins may generate assets that do not originate from on-disk files and are instead synthetic. These type of assets are now supported by generating a cache key based on the output name of the asset. These assets will persist within the cache due to the lack of knowledge on the dependencies of these assets which results in the inability to invalidate the assets. Updated assets of the same output name will, however, replace older versions of the asset on rebuilds. Fixes: angular#21290
filipesilva
pushed a commit
that referenced
this issue
Jul 9, 2021
…sources The asset caching for Angular component resources previously required that all assets had an originating file. However, some Webpack plugins may generate assets that do not originate from on-disk files and are instead synthetic. These type of assets are now supported by generating a cache key based on the output name of the asset. These assets will persist within the cache due to the lack of knowledge on the dependencies of these assets which results in the inability to invalidate the assets. Updated assets of the same output name will, however, replace older versions of the asset on rebuilds. Fixes: #21290 (cherry picked from commit 7536338)
filipesilva
pushed a commit
that referenced
this issue
Jul 9, 2021
…sources The asset caching for Angular component resources previously required that all assets had an originating file. However, some Webpack plugins may generate assets that do not originate from on-disk files and are instead synthetic. These type of assets are now supported by generating a cache key based on the output name of the asset. These assets will persist within the cache due to the lack of knowledge on the dependencies of these assets which results in the inability to invalidate the assets. Updated assets of the same output name will, however, replace older versions of the asset on rebuilds. Fixes: #21290
Can confirm that this is fixed in 12.1.2 - thank you! |
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. |
ikjelle
pushed a commit
to ikjelle/angular-cli
that referenced
this issue
Mar 26, 2024
…sources The asset caching for Angular component resources previously required that all assets had an originating file. However, some Webpack plugins may generate assets that do not originate from on-disk files and are instead synthetic. These type of assets are now supported by generating a cache key based on the output name of the asset. These assets will persist within the cache due to the lack of knowledge on the dependencies of these assets which results in the inability to invalidate the assets. Updated assets of the same output name will, however, replace older versions of the asset on rebuilds. Fixes: angular#21290
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area: @ngtools/webpack
freq1: low
Only reported by a handful of users who observe it rarely
severity5: regression
type: bug/fix
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Yes, the previous version in which this bug was not present was: 11.xDescription
As of Angular 12, the
AngularWebpackPlugin
throws an error when used in conjunction with the git-revision-webpack-plugin. The git-revision-webpack-plugin creates additional outputs that do not specify the optionalsourceFilename
field, but theAngularWebpackPlugin
requires this field.🔬 Minimal Reproduction
A
webpack.config.js
that specifies both plugins will fail:🔥 Exception or Error
🌍 Your Environment
Anything else relevant?
Related issue in the git-revision-webpack-plugin repo: pirelenito/git-revision-webpack-plugin#69
The text was updated successfully, but these errors were encountered: