Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Max one (ideally 0) empty files in Rollup builds #4547

Open
brillout opened this issue Jul 2, 2022 · 0 comments
Open

Max one (ideally 0) empty files in Rollup builds #4547

brillout opened this issue Jul 2, 2022 · 0 comments

Comments

@brillout
Copy link

brillout commented Jul 2, 2022

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant