hyrious
hyrious
I believe this was because esbuild 0.18.0 [adds support for vanilla JavaScript decorators](https://github.com/evanw/esbuild/releases/tag/v0.18.0#:~:text=Using%20experimental%20decorators%20now%20requires) (different from the "experimental" one invented by TypeScript). You just need to add the tsconfig `"experimentalDecorators": true`...
That error was because elastic-apm-node adds [a custom hook](https://github.com/elastic/apm-agent-nodejs/blob/main/lib/instrumentation/index.js) to replace some builtin and thrid-party modules. It redirects the require call to modules like `http` and replace that with [the...
I'm not sure what esbuild needs to do here. Does any other bundler do something similar? If you want to gather bundled dependencies' names, you can enable [metafile](https://esbuild.github.io/api/#metafile).
That plugin (and most esbuild plugins) are meant to run in the Node.js runtime. While your error message seems that you're bundling that plugin into your browser bundle, which is...
The empty object log is fine here since its fields will be computed at the first time you access to it. However if you do catch an empty object at...
The `file` loader is not aimed to return the full path to that file, but to add the file to [assets](https://esbuild.github.io/api/#asset-names) and copy the file to dist folder. Anyway, to...
It is possible to do what you said with the plugin system of esbuild. See this example: ```js import {build} from 'esbuild' import {join} from 'path' await build({ entryPoints: ['src/entry.js'],...
The "what file changed" information in esbuild is maybe not valuable for general users since it's not complete. esbuild implements the custom file watcher that basically polls file system at...
I understand your request. However, [Hot-reloading for CSS](https://esbuild.github.io/api/#hot-reloading-css) only is alreay possible and is documented. The 'change' event sent to browser means the _output_ files changed, not the source changed.
There's a workaround for most feature requests to manual chunks, that you do not enable code splitting, but bundle each entry-points individually: ```ts // src/file1.ts export let a = 1...