Cludge around npm publish

Author: microbit-grace

.github/workflows/build.yml

@@ -24,7 +24,7 @@ jobs:
         env:
           NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       - run: npm run ci
-      - run: npm publish
+      - run: npm publish --allow-directory=all
         if: github.event_name == 'release' && github.event.action == 'created'
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.storybook/main.ts

@@ -2,6 +2,7 @@ import type { StorybookConfig } from '@storybook/react-vite';
 
 const config: StorybookConfig = {
   stories: ['../src/**/*.stories.tsx'],
+  staticDirs: ['../public'],
   addons: [
     '@storybook/addon-links',
     '@storybook/addon-essentials',

public/_headers

@@ -0,0 +1,11 @@
+# Never serve a stale HTML entry point: it references content-hashed assets
+# that are purged on redeploy, which otherwise 404 -> SPA fallback -> a
+# text/html response the browser rejects as a module script.
+/index.html
+  Cache-Control: no-cache
+/iframe.html
+  Cache-Control: no-cache
+
+# Content-hashed assets are immutable and safe to cache forever.
+/assets/*
+  Cache-Control: public, max-age=31536000, immutable