Skip to content
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

Fingerprint assets #15

Closed
oligriffiths opened this issue Jun 9, 2016 · 2 comments
Closed

Fingerprint assets #15

oligriffiths opened this issue Jun 9, 2016 · 2 comments

Comments

@oligriffiths
Copy link

Would it make sense to fingerprint the assets in the manifest. If they're stored in the local browser cache, but they've changed, the mainfest will be updated, but the asset may not be. Not sure the internal workings of if an asset has changed whether it gets re-loaded when the manifest changes...

@krachtstefan
Copy link

Hi @oligriffiths. I'm using broccoli-manifest with ember-cli and as far as I can see the assets in the manifest are fingerprinted if fingerprint is enabled in your current build setup.

@ssured
Copy link
Contributor

ssured commented Nov 24, 2016

The default setting of Ember CLI is to fingerprint assets. This plugin follows the settings of Ember CLI, it does work with fingerprinted assets. I'll close this issue for now. Please reopen if you are having difficulty in working with fingerprinted assets.

@ssured ssured closed this as completed Nov 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants