Evan Wallace
Evan Wallace
> Ideally if `port` is set to `0` then this would just be passed to Go `listen` implementation and it would pick a free random port. I'm not sure that...
Looks like Webpack is changing their non-standard behavior to align with node: https://github.com/webpack/enhanced-resolve/issues/400 and https://github.com/webpack/enhanced-resolve/pull/429. I'm closing this issue because without Webpack, there isn't a strong case for diverging from...
I don't see anything about decorators on the [June agenda](https://github.com/tc39/agendas/blob/main/2024/06.md). Does this need to be added to that agenda for it to be addressed? Sorry, I'm not too familiar on...
Some thoughts: * Angular adds a lot of custom tooling around esbuild, so this is probably a better question for Angular instead of esbuild * You didn't follow the issue...
Closing this issue as it has been `unactionable` without a follow-up reply.
I don't use browserslist myself so I'm not the right person to ask, sorry. A quick search found this thing for you: https://github.com/browserslist/browserslist-useragent-regexp. Does that help? Might or might not...
Not without some manual work on your part. The internal feature compatibility tables that esbuild uses are [here](https://github.com/evanw/esbuild/blob/e87639417e47ba5db160f105785dc10bde0999cf/internal/compat/js_table.go). They aren't intended to be used like that but you could imagine...
Yes, I should do this. The general workaround right now is to have one plugin wrap the other and emulate esbuild's API but that sucks obviously.
I can't reproduce this. Here's what I tried: ```js require('esbuild').build({ plugins: [{ name: 'name', setup(build) { build.onEnd(() => { throw new Error }) }, }], }).then( () => console.log('success'), ()...
This is because esbuild considers throwing an exception to be a side effect, and `new RegExp` can potentially throw an exception (such as `new RegExp('[')`). The string literal is not...