WARNING in webpack-subresource-integrity: Cannot determine asset for chunk scripts, computed="undefined", available=scripts.2b355891e0dd05f2cdd5.js.

[atifsaddique211f]

 ng build --prod --subresource-integrity

                                                                                   
Date: 2019-02-04T14:48:54.230Z
Hash: e8ec25d629e6dd81be68
Time: 119010ms
chunk {0} runtime.76b8cb0dd56312a4d1c7.js (runtime) 2.66 kB [entry] [rendered]
chunk {1} main.36a8afa8424de3afa8ad.js (main) 4.45 MB [initial] [rendered]
chunk {2} polyfills.c6cdf1b91f8032c61d53.js (polyfills) 97.4 kB [initial] [rendered]
chunk {3} styles.51c1ea8fe537fad875ea.css (styles) 283 kB [initial] [rendered]
chunk {4} 4.ecbabf05799fd4bb45c2.js () 3.48 kB  [rendered]
chunk {5} 5.a5a29fb287559e9f39b1.js () 3.63 kB  [rendered]
chunk {scripts} scripts.2b355891e0dd05f2cdd5.js (scripts) 950 kB [entry] [rendered]

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

"@angular/cli": "7.3.0",
 "@angular/core": "7.2.3",
Node : v10.4.1

[jscheid]

Thanks, could you share your Webpack config as well, perhaps in a Gist?

[atifsaddique211f]

@jscheid Here is the content of webpack.config.js in my project root.

module.exports = { node: { path: true, crypto: true, fs: 'empty' } }

[jscheid]

Thanks. Which version of this plugin (webpack-subresource-integrity) are you using?

[atifsaddique211f]

I am not using it directly, I think its a part of Angular CLI 7.3.0
https://github.com/angular/angular-cli

[jscheid]

What does this output?

yarn list | grep webpack-subresource-integrity

or if you're using npm

npm list | grep webpack-subresource-integrity

[atifsaddique211f]

│ └─┬ [email protected] npm ERR! peer dep missing: @angular/animations@^6.0.0, required by [email protected] npm ERR! peer dep missing: @angular/common@^6.0.0, required by [email protected] npm ERR! peer dep missing: @angular/core@^6.0.0, required by [email protected] npm ERR! peer dep missing: @angular/forms@^6.0.0, required by [email protected] npm ERR! peer dep missing: [email protected] - 3, required by [email protected] npm ERR! peer dep missing: popper.js@^1.14.6, required by [email protected] npm ERR! peer dep missing: [email protected] - 3, required by [email protected] npm ERR! peer dep missing: popper.js@^1.12.3, required by [email protected]

[jscheid]

Ok, you need to upgrade it. Try npm upgrade webpack-subresource-integrity and make sure it gives you the latest version (1.3.2).

[atifsaddique211f]

okay, sure,
I try.
Thanks

[atifsaddique211f]

It don't upgrade like that, I think its a part of some sub dependency, and it is not getting upgrade like that from project root.

[jscheid]

Right, it's because angular depends on an older version of this plugin, which I believe they do because they disagree with #90.

You could work around it by switching to yarn and specifying an override. The following might work but I haven't tested it:

{
  "resolutions": {
    "webpack-subresource-integrity": "^1.3.2",
  }
}

I'm going to close this because the only thing I could do to help is revert #91 or maintain a separate branch, and I'd only do that after further discussion (on ticket #90). Please do let me know if the workaround helps, though.

[atifsaddique211f]

@jscheid simple resolution with yarn didn't work.

atifsaddique:CTEMPLAR_FRONTEND atifsaddique$ yarn list | grep webpack-subresource-integrity │ ├─ [email protected] ├─ [email protected]

[jscheid]

Thanks. The grep result you've posted doesn't conclusively show that it didn't work, I assume you've tried re-running the build and it ran into the same error again?

[atifsaddique211f]

Yes

On Wed, 6 Feb 2019 at 2:11 PM, Julian Scheid ***@***.***> wrote: Thanks. The grep result you've posted doesn't conclusively show that it didn't work, I assume you've tried re-running the build and it ran into the same error again? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#104 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIdItOPeJJ61jR3bhi1cEcTBvSahnYprks5vKpw5gaJpZM4ahXOG> .

-- Best Regards Atif Saddique

[jscheid]

@atifsaddique211f the upgrade works fine in my test, see https://gist.github.com/jscheid/29dee9816e89a27c71b54fd40719a70f

If it still doesn't work for you I'm happy to take another look. I'll need the following from you:

• A current copy of your yarn.lock
• Updated output of ng build
• Ideally, a repository that demonstrates the issue

[vishalhulawale]

I am also getting same warning on ng build --prod
I am having **1.1.0-rc.6 ** version of webpack-subresource-integrity.
I tried npm upgrade webpack-subresource-integrity it did not solved this issue.

[jscheid]

@vishalhulawale npm upgrade won't work. You need to be using yarn and specify resolutions in package.json as detailed above. See the gist for a working example.

[adarshaj]

For those that are facing this due to angular, the issue is being sorted out at angular/angular-cli#9338 (essentially the above solution by @jscheid is not updating the dependencies recursively, so the cli package should fix the version in their dependency).