Under certain circumstances, such as opening an example from the docs, multiple versions end up being set in parallel - the original version on startup, immediately followed by the version specified for the example being loaded. Once they're running in parallel, they can collide on setting the active version on disk with fiddle-core.
This situation could be improved by:

Under certain circumstances, such as opening an example from the docs, multiple versions end up being set in parallel - the original version on startup, immediately followed by the version specified for the example being loaded. Once they're running in parallel, they can collide on setting the active version on disk with
fiddle-core.This situation could be improved by:
@electron/getat this time. Aborting an in-progress version being set should at least not conflict with any subsequent versions set.