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
On top of a primary build using vite.config.js (for multiple pages app) I execute a secondary build script (a build.mjs file) to get several JS files from another source directory into same output dist folder.
With Vite v3.1.2 (and prior) I do not have an issue and output js files are written to dist next to files coming from a previous step as expected.
However after I updated to v3.1.3 today, erroneous output files are written on top of previous ones.
As if Js files of secondary source folder are matched to each input of rollupOptions in defineConfig argument of vite.config.js.
I've prepared an example project with two NPM scripts.
You can see the problem running
npm run build: only runs on src folder and then
npm run two-builds that executes a custom build script on a secondary source folder after previous default.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
Describe the bug
On top of a primary build using
vite.config.js
(for multiple pages app) I execute a secondary build script (abuild.mjs
file) to get several JS files from another source directory into same outputdist
folder.With Vite v3.1.2 (and prior) I do not have an issue and output js files are written to
dist
next to files coming from a previous step as expected.However after I updated to v3.1.3 today, erroneous output files are written on top of previous ones.
As if Js files of secondary source folder are matched to each
input
ofrollupOptions
indefineConfig
argument ofvite.config.js
.I've prepared an example project with two NPM scripts.
You can see the problem running
npm run build
: only runs onsrc
folder and thennpm run two-builds
that executes a custom build script on a secondary source folder after previous default.Reproduction
https://github.com/bogacg/vite-3-1-3-js-build-api-bug
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: