Ives van Hoorne
Ives van Hoorne
Hey! Thanks for the contribution, do you have an example where we're currently not parsing/rendering this correctly?
I think that this has to do with our `Same-Site` cookie setting, and with how the browser handles it. It could be that the browser clears it out of safety.
@OnkelTem could you share the version of the editor (shown in the bottom left)? I think we fixed this issue (https://github.com/codesandbox/codesandbox-client/issues/8078) recently but you might be stuck on an old...
Good point! The tricky thing about enabling "production mode" is that we don't do the uglifying/tree-shaking, so we need to communicate clearly that we're only changing the environment variable there...
Yep. We haven't reimplemented Netlify/Vercel yet with the new APIs. In the meantime, it is possible to do this with devboxes. You can do this either by: 1. Running the...
Oh, I think this would break existing URLs. Because v2 doesn't support directory imports yet. We're working on that right now, btw!
Heya! We use CodeSandbox servers for one thing: the preparing of dependencies. You can host everything in the sandbox folder somewhere else and point the bundler to it and it...
This was a great read! Cleared up a lot for me.
I think I know why this is happening. Since we use the static template, we don't add much custom pieces of CodeSandbox in there. The browser mixes iframe and parent...
It only changes the TypeScript version used by the bundler right now. It's not in the editor yet, as it would require us to dynamically update the VSCode Extensions. I...