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
A Rollup build can contain only one empty file (or better yet no empty files at all).
Actual Behavior / Situation
A Rollup build can contain many empty files.
Modification Proposal
In principle, it should be possible to have only one empty file and point all empty entries to that empty file.
Ideally, there wouldn't be any empty files. But I guess there is a need to point empty entries to empty files. An alternative would be a isEmpty flag (I've read such a flag in some PR but can't find any reference to it in the Rollup docs) while not pointing to any file. I can see that being a breaking change though.
It's low priority, although it is confusing for users to see a bunch of empty files in the build.
Expected Behavior / Situation
A Rollup build can contain only one empty file (or better yet no empty files at all).
Actual Behavior / Situation
A Rollup build can contain many empty files.
Modification Proposal
In principle, it should be possible to have only one empty file and point all empty entries to that empty file.
Ideally, there wouldn't be any empty files. But I guess there is a need to point empty entries to empty files. An alternative would be a
isEmpty
flag (I've read such a flag in some PR but can't find any reference to it in the Rollup docs) while not pointing to any file. I can see that being a breaking change though.It's low priority, although it is confusing for users to see a bunch of empty files in the build.
Reproduction: https://github.com/brillout/rollup-multiple-emtpy-build-files.
(Btw. thanks for all your wonderful work on Rollup. And funny that Lukas foresaw a Rollup wrapper before even Vite came out.)
The text was updated successfully, but these errors were encountered: