dimanche 26 mai 2019

ember assets - "public" assets should not be fingerprinted but they are?

In my Ember.js 3.8 project I have an image file in :

/public/assets/images/foo.png

... According to this (admittedly a little out of date) files put in public/assets/images should be available unchanged when referenced as assets/images.

This is up to date, a little less explicit but says that items placed beneath public will end up beneath assets.

When I do a production build the file I have in /public/assets/images/ ends up /dist/assets/images/ but with a finger print, eg foo-97cf8c0765aefa517d22e1fc71f43d6e.png.

Am I meant to explicitly suppress the finger-printing ? The doco seems to suggest that's not necessary ?




Aucun commentaire:

Enregistrer un commentaire