Stable update.
It's only enabled by default for new projects. Existing projects won't see any change. It was also enabled by default for a while last year before it got disabled again due to a Chrome bug, so it's already been pretty widely tested.
I love the idea and do think it's a good move to make it default, but it does produce some _slightly_ different results that should be considered (mostly within documentation). For example, this page in the manual shows how you can add an `alert` to the events sheet via scripts, but this won't work while in worker mode since the webworker doesn't have access to alert:
construct.net/en/make-games/manuals/construct-3/scripting/using-scripting/scripts-in-event-sheets
Fairly minor overall, but definitely something to note.
Note worker mode is documented in the scripting section of the manual under JavaScript in Construct. Also if you create a new project and choose to start with script, it leaves worker mode off, so you can still directly access DOM methods like alert.
My concern is more with beginners creating a new project and adding an unsupported 3rd party plugin to it, wondering why it's broken. I feel like it might be a good idea to have a flag or something similar inside the addon SDK, that indicates that worker mode is supported.
This could for example be used to display a warning message, that selected 3rd party plugins might not support worker mode.
I'd rather require addons are compatible than let addon developers get away with making ones which are broken with certain settings.