Option to read assets on startup #2943
Unanswered
cyberalien
asked this question in
Q&A
Replies: 1 comment
-
|
I understand that you want to make public assets from previous builds to the new one in order to allow them being served for clients currently loading older manifest. Nuxt in particular implemented a build manifest mechanism to detect new builds and vendors such as Vercel Skew Protection in order to answer this common problem. If you have older build files available, there is another way of adding an additional public dir so that nitro picks and merges it during build. It merges them. {
publicAssets: [{ baseURL: "/_nuxt", dir: "path/to/previous/build/public" }],
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature
Currently when building in Nuxt, Nitro caches list of assets in
server/chunks/nitro/nitro.mjsand serves only those assets, ignoring actual contents ofpublic.However, I want to keep serving static assets from previous deployment, which are in
publicdirectory. It would be awesome if there was an option to readpublicdirectory on startup instead of serving hardcoded set of assets.Additional information
Beta Was this translation helpful? Give feedback.
All reactions