You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i developing frontend part of this project i need this index.html because of possibility to run it and watch changes in browser in real time.
When i building it for serving from backend i don't need in index.html, it will be generated by my golang backend, but i need all other files from frontend.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a project which is spa, it have a very basic structure:
When i developing frontend part of this project i need this index.html because of possibility to run it and watch changes in browser in real time.
When i building it for serving from backend i don't need in index.html, it will be generated by my golang backend, but i need all other files from frontend.
I wrote this
config in vite.config.ts file as was recommended in this discussion and it works very close to behavior i need.
The problem is that given config builds with structure
when generated js asks for this assets from
path.
I can't believe that there is no solution for normal spa building and bundling with vite.
Will be happy with some help.
Beta Was this translation helpful? Give feedback.
All reactions