CodeSandbox (or similar) starter template for bug reproductions

[nrayburn-tech]

Some bug reports would benefit from a reproduction that can be tested against. Providing a started CodeSandbox that is already configured it should be easier to get reproduction cases from end users. Oxlint is what I'm noticing this with and would like to see a CodeSandbox template for, but I think most of the tools could benefit from something like this.

CodeSandbox is what I see most often, but I think anything could work. The Oxc Playground works for single file reproductions, but for reproductions requiring multiple files it isn't sufficient.

[camc314]

we probably want to expand https://playground.oxc.rs to make it more granular to enable/disble rules (currently its just linter enable/disable)
but a codesandbox would also be useful for issues especially config ones

[nrayburn-tech]

I did some experimenting and was able to get a template CodeSandbox mostly working. There are a few errors on startup, but they can be ignored.
The primary concern with CodeSandbox is that it has a limited free tier which could be an issue for Oxc contributors running the sandboxes to investigate an issue. I believe it is about 40 hours per month of free usage, so maybe this isn't a big concern.

I also did some experimenting with StackBlitz (which Vite uses). I was unable to execute the Oxlint CLI due to an error that I didn't really understand, so that's obviously a pretty big blocker if Oxlint doesn't work in that environment. Other than that, I don't think there are any usage limits with StackBlitz. StackBlitz can also create an environment directly from code within a GitHub repo, example in my Oxc fork here.

StackBlitz error if anybody has any insight.

oxlint --config .oxlint.json ./src
/home/projects/nrayburn-tech-oxc-dozjma/node_modules/@oxlint/linux-x64-gnu/oxlint: line 2: "foo(" must be followed by )