hashed file names

First time using rollup so excuse the ignorance. Is it possible to export bundle.js/.css with hashed names so the browser doesn’t serve cached versions when I push to production? How would this work updating public/index.html

[maxmilton]

For general support questions you’re better off asking on sites like stackoverflow.com. Github issues are for reporting bugs or feature requests etc.

About your question, please read the rollup docs:

• https://rollupjs.org/guide/en/#outputentryfilenames
• https://rollupjs.org/guide/en/#outputchunkfilenames
• https://rollupjs.org/guide/en/#outputassetfilenames

[crisward]

I realised this is a closed issue. But it was the first one that appeared when googling, so I thought I drop a solution here for anyone who finds it useful (including future me…)

I found that the css object passed to the css function holds a hashed filename the same as your entry file, including the hash, but with the css extension.

So the below would output index-[hash].js and index-[hash].css

//excerpt of rollup.js

export default {
	input: 'src/index.js',
	preserveEntrySignatures: false,
	output: {
		sourcemap: true,
		format: 'es',
		name: 'app',
		dir: 'build',
		entryFileNames: '[name]-[hash].js'
	},
	plugins: [
		svelte({
			// enable run-time checks when not in production
			css: css => {
				css.write(css.filename);
			}
    })
  ]
};

Also because I’m loading my css into a webcomponent, I parse the css filename by inspecting the module filename and swapping .js for .css

//index.js
let css_filename = import.meta.url.match(/[^\/]+\.js$/)[0].replace(/\.js$/,".css")

See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import.meta for more info on this.