Evan Wallace

> * Tests pass (some have no test files, which I assume is ok) > > > After putting the executable made from `gmake esbuild` in PATH, it works just...

Ah, sorry. The version of Go that esbuild 0.19.5 used was Go 1.20.10, not 1.21.1.

Unfortunately esbuild is not a JavaScript run-time, and this feature might not be a good fit for esbuild. You may be interested in Bun though, as it does have something...

> Using these targets will result in aliases to the related browsers like `baseline2022 == [chromeX, firefoxX, safariX]` I looked pretty hard for this data for ~30 minutes and couldn't...

I asked and sent feedback and got an excellent reply in the thread linked above. It seems like perhaps this isn't a good fit for esbuild after all. The definition...

I just tried it out. It looks like the sample code needed to get this to work is pretty much the same: ```js import * as esbuild from 'esbuild' import...

I'm closing this issue because esbuild is working as intended here. I agree that [inject](https://esbuild.github.io/api/#inject) is likely the best fit for your use case. The difference is that `define` inlines...

https://jsr.io/docs/publishing-packages says this: > **npm packages are supported**: You can depend on npm packages by either specifying them in the `dependencies` of your `package.json`, or by referencing them in code...

> So I don't think "import 'echarts/lib/util/format';" is wrong. I think auto add extension ".js" is also needed when use the "*" match in package.json. I think `import 'echarts/lib/util/format'` isn't...

This comment is relevant: https://github.com/evanw/esbuild/blob/51f67d4523bdea1e224753078b03dc12ea0ec70b/internal/js_parser/js_parser_lower.go#L284-L313