David Zearing
David Zearing
Just to be clear, I'm interpreting that the only way to add live reloading (for now) is to avoid `.serve()` altogether and only use `watch` mode with `live-server` hosting the...
@zaydek Oh! I totally forgot there's a config setting to use in-memory building - so yeah, I could probably use watch mode, then have express serve up the script from...
Hmm. I am using `write: false` to avoid writing content to disk, but there doesn't seem to be way to access the in-memory output (`result.outputFiles`) in watch mode. Seems like...
@zaydek Mainly I'd love to minimize disk writes and make the inner loop `yarn start` experience as fast as possible. I could certainly write to disk, maybe that could even...
Nevermind on the above `outputFiles` comment - it does look like `outputFiles` is showing up in the result. I think it was my bad and I didn't save the `write:false`...
One minor note; perhaps title should read "re-exported namespaces cannot be tree-shaked". If you export * from the source rather than the namespace itself as a named export, tree-shaking does...
FWIW, this still repros @ 0.14.13.
May be related to: https://www.engadget.com/2018/03/30/google-shutting-down-goo-gl-url-shortening-service/
@alexander-akait to clarify: This is certainly related to #2933 in that I'm enabling the experimental module output. I did expect a re-export, and I'm just filing the bug to track...
The scenario where we use this is: * We have a component library consists of many components. Each component is in a separate package. * App devs just import {...