Appending hash to imported files name

[alexbidenko]

Background

When we use nuxt assets file import, in production mode nuxt appending file hash to files name. It is very useful because browser can understand when file has changed by filename - it is necessary for right caching for example.

But nuxt-content-assets plugin copy files only and do not append hash to its names. If I have used browser cache mechanism (for example by cache-control header) and then will have changed file (but not filename) - in browser I will have seen old image.

Proposal

It would be great if nuxt-content-assets added a hash of files to its filename (maybe with some enabled option in nuxt.config).

[davestewart]

Hey Alex,

In a pre-release version of the module I had a full assets path template system implemented:

• https://github.com/davestewart/nuxt-content-assets/blob/c9c92767fa4fa83ceeaf99dd3e226b0fcf9a533b/README.md#output

...which I am considering bringing back.

Would this solve your problem?

[alexbidenko]

@davestewart , yes, it is looks like something great that I need exactly :)

Did I understand correctly that these changes can be expected soon in nuxt-content-assets?

[davestewart]

Hey Alex,

Short answer: probably.

Longer answer: I took it out as juggling paths was getting a bit complicated when I was iterating on the original concept, but I hope that it will still be viable to put it back in. I just need to find the time to reimplement, test and document.

Are you OK without the feature for now? What would be your ideal timescale?

[alexbidenko]

@davestewart , Without the hash feature I prefer to use paths to nuxt public folder and change filenames every time when I have changed files (for cache-control header optimization mechanism). It is because public folder as file storage more transparent for understanding by my colleagues.

But I like nuxt-content module and your nuxt-content-assets plugin is very perspective! I hope you can solve all your problems and your module will getting even better :) I'm willing to wait for updates to your plugin as long as necessary and use it in the future when the hash feature would be ready to use.

[davestewart]

Hey @alexbidenko,

Sorry for the huge delay – I'm working on this tomorrow. I'm just checking if you still use Nuxt Content Assets, and if you have any more information / context for me before I start?

[alexbidenko]

I don't have any further information on this matter. However, using the Nuxt Content and Assets module is still relevant to me, especially if it solves the problem I mentioned :)

[davestewart]

I'm on it!

[davestewart]

Hey @alexbidenko – sorry; I started typing a reply but forgot to send it.

Long story short, it was trickier than I expected to re-integrate the helper I shared previously.

I see this as "nice to have" rather than a bug, so I'm probably going to push this back until I have more time.

Also, I would like to start work on Nuxt Content 3 compatibility, so if it happens that I find some architectural win as I migrate the lib, I will try and back port to v1.10. Sorry I can't give you the good news!

Keeping this open for now.