Ives van Hoorne

Opening this issue again, because I think there should be a way to disable eslint on a sandbox if it's not behaving as expected.

Hmm, I don't think this one's true. If you have read access, you should still be able to fork because that's how you get your own version to work on...

Hey @oliversturm! You're right, I think in this case it would be best to use a container sandbox, since there's a server component to it. The svelte implementation that we...

Yep, the template determines how our in-browser bundler will transpile the project. In Svelte's case, we're adding a transpiler that can convert `.svelte` files to its corresponding JS (similar to...

Could you try again? I've deployed some extra error logging and improved the errors that we return. It might work now, or at least return a descriptive error. On Mon,...

Oh this is super useful! It seems like it tries to create a commit on the "main" branch though the repo has only a "master" branch. I can take a...

Oh good one, thanks for reporting it! We'll take a look at it! In the meantime, I've cleared the cache of the sandbox so it gives back the correct files.

Swooping in! (I heard CodeSandbox 😂) In the future, CodeSandbox should be able to run Elixir as well. At CodeSandbox we're currently experimenting with this (our backend is in Elixir/Phoenix),...

Hey! The commit in our fork fixed the issue. That said, we're removing the fix in a future version where we rely on UFFD to handle page faults. We've updated...

A fix for this should launch in about a month. The challenge here is that we're running ESLint in the browser, and for that we had to apply some patches...