asset-mapper
v1.0.2
Published
Reduce cache churn by generating stable file names, manually hashing them, and providing a manifest by which to read the hashed assets. This is generally intended for importmaps, but could have other applications as well.
Downloads
32
Maintainers
konnor_rogersReadme
Purpose
Reduce cache churn by generating stable file names, manually hashing them, and providing a manifest by which to read the hashed assets. This is generally intended for importmaps, but could have other applications as well.
For more info checkout this issue: https://github.com/sveltejs/kit/issues/4482
And this reading: https://philipwalton.com/articles/cascading-cache-invalidation/
https://jspm.org/import-map-cdn#the-javascript-module-caching-tradeoff
Installation
npm install asset-mapper
# OR
yarn install asset-mapper
# OR
pnpm install asset-mapperVite Usage
// vite.config.js
import { RollupAssetMapper } from "asset-mapper"
export default {
build: {
rollupOptions: {
input: {
// ...
},
output: {
entryFileNames: `[name].js`,
chunkFileNames: `chunks/[name].js`,
assetFileNames: `assets/[name].[ext]`
}
outdir: // ...
},
},
plugins: [
RollupAssetMapper()
],
}Checkout SvelteKit
Right now there is a patch package in place to change from hashed files to unhashed files. Perhaps theres a way to fix it with config, but I wanted to get a quick prototype.
git clone https://github.com/konnorrogers/asset-mapper.git
pnpm run setup
cd tests/fixtures/svelte-kit
pnpm run buildThen go to: .svelte-kit/output/client/asset-mapper-manifest.json to see the built assets.
Going 1 step further
While this doesn't quite solve the "cache-invalidation" issue, its a step in the right direction.
The next step is to use the generated manifest to construct your own "importmap"
Example:
<html>
<head>
<script type="importmap">
{
"imports": {{ fs.readFileSync("asset-mapper-manifest.json") }}
}
</script>
</head>
<body></body>
</html>