Evan Wallace

> https://esbuild.github.io/try/#YgAwLjIwLjAALS1zdXBwb3J0ZWQ6bmVzdGluZz1mYWxzZQBlAGVudHJ5LmNzcwA6Oi13ZWJraXQtc2Nyb2xsYmFyLXRodW1iIHsKICAmOndpbmRvdy1pbmFjdGl2ZSB7CiAgICBiYWNrZ3JvdW5kOiByZWQ7CiAgfQogICY6aG92ZXIgewogICAgYmFja2dyb3VuZDogYmx1ZTsKICB9IAp9 > > This also looks broken. I don't think this case is supposed to do anything because [the nesting selector cannot represent pseudo-elements](https://www.w3.org/TR/css-nesting-1/#ref-for-matches-pseudo%E2%91%A0). I believe this is because...

Closing as by design, just like #2647.

The metafile is the way to do this with esbuild. I'm not going to built support into esbuild itself for each individual build metadata task that people want to do....

> The blocker here is that the metafile (unless you can tell me otherwise and I’d be very happy for you to!) does not include version numbers for the included...

The browser does not provide packages such as `os`, so these packages are not available when building for the browser. If you want to substitute them for other ones, you...

It would be wonderful if this bug in Go was finally fixed. However, I believe your fix would be irrelevant for esbuild as esbuild had to fork the entire Go...

Closing as this question has been answered.

I understand why you'd want this, and this is kind of a neat way to do it. However, having the compiler automatically remove safety checks kind of reminds me of...

Closing this for the reason described above. This seems like too much of a foot-gun to me.

This is similar to an existing issue: #475. The linker would ideally merge duplicate imports. However, this gets complicated with top-level await so doing this is not as straightforward as...