Vite asset misses some files when processed
See original GitHub issue- Laravel Version: 9.26.1
- PHP Version: 8.1.6
- Database Driver & Version: N/A
Others:
- NodeJS v16
- OS Windows 10
I followed the documentation about processing static assets to process my static asset files. However, some files were missed by vite.
My files contains a lot of repeated filenames and identical structure, with only difference is the origin name of the directory, like example:
resources/
static/
subdomain-a/
logo.png
logo-alternate.png
...
subdomain-b/
logo.png
logo-alternate.png
...
subdomain-c/
logo.png
logo-alternate.png
...
...
Issue Analytics
- State:
- Created a year ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Missing components and assets · Issue #2454 · vitejs/vite
Describe the bug. I was being able to do a functional build with vite@1 and now that I have updated my configuration and...
Read more >Vite not copying all static assets - Laracasts
I've already debugged the function "assetFileNames" and the files which are missing are processed and the right path is set. Altough they won't...
Read more >Static Asset Handling - Vite
Referenced assets are included as part of the build assets graph, will get hashed file names, and can be processed by plugins for...
Read more >Missing components and assets in vite@2 build - Stack Overflow
Solved! This was happening because vue-router's createWebHistory() can't hanlde the navigation if the app is not being served.
Read more >Configuring Vite - Vite Ruby
Vite Ruby leverages a simple config/vite.json configuration file, which is read both from Ruby and JavaScript, and allows you to easily ...
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
Transferred this to the vite-plugin repo.
Just a heads up that the upstream fix for this has now been tagged in vite
3.2.0
.