Vite issue building for production when lib.entry item has dot in the name
When building for production, asset files are not bundled with the right path/file name when dot is present in entry name
Why rollupOptions.output.compact would cause Vite build error on Chrome 62?
Vite config: build.rollupOptions.ouput.compact: true.
@rollup/plugin-alias How to use relative paths?
I just switched from Next.js to Vite, but I found a problem with the file path.
How do I prevent Vite/Rollup from amending my js filename with the number 2 becuase it has the same name as a css file?
I have php-based API that serves HTML, CSS and JS files to another site for interactive visuals. Bundling was originally done by Mix. I am trying to switch over to Vite.
Create npm packages via Vite the right way
I want to create a monorepo which will include some packages and will have the following folder structure: