Prerender fails when Vite build.assetsDir option is specified
See original GitHub issueSteps to Reproduce:
- add build.assetsDir option to vite.config.js with any path other than the default “assets”
- run vite build followed by prerender command
- Observe that an error is thrown originating in
collectAssets
in/dist/getPreloadTags.node.js
Expected Results:
Customizing the assetsDir should successfully prerender the site into the customized directory
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Build Options - Vite
assetsDir #. Type: string; Default: assets. Specify the directory to nest generated assets under (relative to build.
Read more >Options for assets building without adding hash #378 - GitHub
I'm trying to make a library builder out of create-vite-app , and it is close to useable with one last step, here's the...
Read more >Vite - change ouput directory of assets - Stack Overflow
I need to create a different folder for js and css files under assets . In other words, I need to put js...
Read more >Pre-rendering (SSG) - vite-plugin-ssr
Pre-rendering means to render the HTML of our pages at build-time (when we run $ vite ... We opt into pre-rendering by setting...
Read more >How to build and deploy with Vite JS - YouTube
What Is Vite ? Vite is the French word for fast and is a Javascript development server and bundler that delivers source files...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
AFAICT, this should fix it. I will release later today.
Also btw if you need something from me, feel free to push. I don’t mind.