David

Not stale

+1 on the documentation. I see the `--config` option was implemented, but when I run it I get an error with the old syntax ```sh ❯ ~/Downloads/swc-darwin-arm64 compile --config=jsc.transform.react.importSource=@emotion/core error:...

Thanks @alexeagle and @realtimetodie . So it looks like the `--config` now takes a json object instead of a dot notation object when switching between the node and rust based...

This concept would be beneficial for things that build with `javascript` as well. We are using `rules_js` and while generally the build file generation that Aspect provides is good, there...

@1000ch last one I swear. Same question as the other two. Would you be willing to accept this feature if I rebase and fix the conflicts?

Looks like the easiest way out of this is with this line https://github.com/browserslist/browserslist/blob/4db22aed0f0453b73fabc87264bf7210d101075b/node.js#LL367C21-L367C49 Is that accurate? Setting `process.env.BROWSERSLIST_IGNORE_OLD_DATA` to `true` would skip this check right?

@sindresorhus If you have a moment, this is a quick fix that would allow my team to pull in the binary without having to have a bunch of tools to...

@1000ch Same as https://github.com/imagemin/pngquant-bin/pull/126, would you be willing to accept this feature if I rebase and fix the differences?

The custom resolve function on a loader sounds promising if it works and prevents nodejs forking which would be not ideal if it can be avoided.

`workspace:*` is used by pnpm and abides by the spec for workspaces. https://pnpm.io/workspaces The way it works is it will grab an internal version of the dependency in the workspace...