Skip to content

fix(@angular-devkit/build-angular): update webpack-subresource-integr… #14514

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

Closed

Conversation

matdryz
Copy link

@matdryz matdryz commented May 24, 2019

@matdryz matdryz marked this pull request as ready for review May 24, 2019 07:49
@alan-agius4
Copy link
Collaborator

The reason why this is blocked is because this version has a peer dependency of html-webpack-plugin. Which is not used in the CLI.

@matdryz
Copy link
Author

matdryz commented May 27, 2019

Isn't it OK since it is an optional peer dependency?

@clydin
Copy link
Member

clydin commented May 28, 2019

Optional peer dependencies functionally don't exist since they are not standardized nor supported by npm.

@fabioemoutinho
Copy link

would be great to get rid of the following error:

WARNING in webpack-subresource-integrity: Cannot determine asset for chunk scripts, computed="undefined", available=scripts.95488a83006a892d75cd.js. Please report this full error message along with your Webpack configuration at https://github.com/waysact/webpack-subresource-integrity/issues/new

@alan-agius4
Copy link
Collaborator

Superseded by #15592

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants