ConfigurationEdit this page
You can configure sandboxes and other options with configuration files specified by the template.
We think that configuration is used when a program can't understand what the user really wants, and try to steer away from it as much as possible. However, there are always advanced use cases where the user wants to control every aspect of their program, and thus configure everything. CodeSandbox is a clear example of a program that requires configuration, it doesn't fit the 95%.
That's why we introduce a concept called 'Configuration Files'. Every template on CodeSandbox has a list of configuration files it supports. You can see this list in the sidebar:
Some configuration files can be configured using a UI. This UI will generate a configuration file based on its state.
A sandbox can be configured too, you can do this with
support these options:
|Option||Description||Possible Values||Default Value|
||Whether we should throw an error if we detect an infinite loop||
||Whether we should refresh the sandbox page on every change, good for sandboxes with global state.||
||Which sandbox template to use||see here||smart detection, w/ fallback to