Jason Miller

Microbundle doesn't support custom Rollup configuration - allowing that would make it impossible to provide an upgradable preconfigured system. FWIW there shouldn't be a reason to compile the `less` from...

@danielweck yes, I think this is related to our use of `worker_threads`. I'm thinking it may be [the Node/glibc bug described here](https://github.com/parcel-bundler/parcel/pull/7461/files#diff-63cc632e8b7bbfd555a71cd835b456bcb33f17773175f2dc42e288fcd38db7e3R40-R43). What type of Nodejs installation are you using...

Indeed - right now I have to run microbundle multiple times in order to handle disparate input-output flows.

I think I'd prefer to have Microbundle generate directories with derived `package.json` files like Kent's solution. It would be difficult to infer when a file needs to be treated as...

Ah but there is, just it's only for multiple entries: their names and locations are mirrored in `dist` and they are automatically treated as externals of eachother.

This is my most wanted feature 😄

Can we enable compression and sourcemaps for `--target web` by default? I know there's a bunch of people using Microbundle for Node, but it's still primarily used to bundle packages...

That ignores the unpkg.com use-case. Also lots of folks don't have their bundlers configured to optimize to the same extent. In cases like Preact, nobody on earth has their bundler...

Circling back to try to unblock this: There are some transforms we currently use Terser for that genuinely can't be left off by default, especially if we produce both minified...

There is no way to accurately determine locality of property usage, short of building a complete partial evaluator like Closure, and even then it can't be done without additional information...