Evan Wallace

There's an interesting problem with doing this: #1063. If the initial build fails due to a plugin throwing an error, esbuild doesn't necessarily have enough information to know what to...

This is definitely something I plan to get to because I want to be able to use it myself. Right now `import(path)` turns into `Promise.resolve().then(() => require(path))` so dynamic imports...

I don't have a specific date but I'm currently focused on a rewrite of the bundler to enable code splitting, tree shaking, ES6 module export, and a few other features....

> Do you have any news about this? It's mostly working already. The chunk splitting analysis has already landed. All that's left is to bind imports and exports across chunks....

I just released version 0.5.15 with an experimental version of code splitting. See [the release notes](https://github.com/evanw/esbuild/blob/57d6f87e089f44404df5040d2b8a0a12815b6d60/CHANGELOG.md#0516) for details. It's still a work in progress but it's far enough along now...

> Simple CSS support is the next main thing we are eaglerly looking forward to. You and me both! CSS support is currently the next major feature I want to...

That's great to hear! Thanks so much for trying it out.

I have a small progress update on code splitting. From the [release notes](https://github.com/evanw/esbuild/blob/dcf5560798913575060e6279efc14cb79771cab5/CHANGELOG.md#unreleased) for the upcoming release (not out yet): > Code that is shared between multiple entry points is...

Another code splitting update: I finally got around to implementing per-chunk symbol renaming, which I view as required for the code splitting feature. I've made several attempts at this in...

> @evanw it would be very interesting if you could expand somewhere on the exact symbol naming technique you converged on here. I just wrote up some documentation about the...