Multiple entry points - Githubissues

mattdesl / budo

:clapper: a dev server for rapid prototyping

MIT License

2.18k stars 106 forks source link

Multiple entry points #139

Open webholics opened 8 years ago

webholics commented 8 years ago

It would be great if budo would support multiple entry points like:

budo src/index.js:static/bundle.js src/lib.js:static/lib.js

mattdesl commented 8 years ago

This would be cool but it's technically difficult, and opens up a lot of questions:

Currently that syntax is used to concat multiple files into the same bundle, like budo test/*.js --serve bundle.js – both features can't exist in tandem without new syntax
This would be a pretty drastic breaking change; we would no longer use the --serve argument, but instead each entry would have to specify its own (optional) script src URL
How to handle duplicate modules between the two bundles?
Does this mean we spin up multiple instances of watchify?

webholics commented 8 years ago

Ok I understand. Its just that we were coming from beefy and wanted to transfer our dev workflow to budo. Beefy supports multiple entry points but the live reloading of budo is much better.

mattdesl commented 8 years ago

I'm open to discussing it further and integrating something if we can find a nice solve. :smile:

webholics commented 8 years ago

I did some research, and beefy indeed starts multiple instances of watchify when provided with multiple entry points. It does not explicitly handle duplicate modules between the two bundles (I also would prefer to not do anything magical in this case).

I understand that its quite difficult to implement with the current budo api. Maybe we'll just bundle everything in dev mode.

kumavis commented 5 years ago

:+1: do want also transitioning from beefy with multiple bundles

cosmikwolf commented 3 years ago

+1 would love to have multiple entry points. looking for a new solution, might have to check out beefy...