You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hash of files are not update between rebuilds when running the Ember CLI server in production mode.
Background: I'm caching the asset with a service worker. Ember CLI SRI does update the integrity hash between rebuilds, this causes the changed asset to not load.
To reproduce:
ember new test-app
cd test-app
ember s --prod
Now open localhost:4200 and note down the hash of test-app.js.
ember g component foo-bar
App reloads, note that the hash of test-app.js is still the same.
Now kill the test server and serve again with ember s --prod. Now the hash of test-app.js did change.
The text was updated successfully, but these errors were encountered:
We're running into issues with resource integrity as well. The current issue we're facing is the content of the css differs, but the md5 hash in the file is exactly the same:
This is a big issue since the initially generated file is cached long term on our CDN which means the old content is returned. This clashes with the expected integrity:
Edit: This happens for us on Heroku deploys (potentially the same as @Exelord), not on ember serve.
Edit 2: I've created issue #118 as this does not seem directly related to ember s --prod
The hash of files are not update between rebuilds when running the Ember CLI server in production mode.
Background: I'm caching the asset with a service worker. Ember CLI SRI does update the integrity hash between rebuilds, this causes the changed asset to not load.
To reproduce:
Now open
localhost:4200
and note down the hash oftest-app.js
.App reloads, note that the hash of
test-app.js
is still the same.Now kill the test server and serve again with
ember s --prod
. Now the hash oftest-app.js
did change.The text was updated successfully, but these errors were encountered: