This is awesome, and my 2 cents are that Electron by default should cache on the first startup as much as possible because an Electron app deserves to be cached right from the beginning, as opposed to any website I visit.

Release Notes Persisted

V8CacheOptions is a new webpreference option to enforce code caching policy

I have automatically backported this PR to "10-x-y", please check out #23867

I have automatically backported this PR to "9-x-y", please check out #23868

I have automatically backported this PR to "8-x-y", please check out #23869

Couple of things to remember,

• This flag only affects scripts served by chromium in the render process, scripts served by Node.js will not be affected.

• If your app uses service workers to serve resources, then you need not use these flags. You will get the more aggressive code caching for free.

• bypassHeatCheck is a sane default for all electron apps.

• bypassHeatCheckAndEagerCompile should be used cautiously, depending on the amount of code being eagerly compiled and cached, it can cause increase in memory and add to GC pressure, also causes increased time in deserializing the cached data which translates to increased code load time and then there is bytecode flushing GC that will clear up inactive code, so most of the cached data may not end up being used.

Should this be the default?

Electron 11 is set to be a quiet release, so we don't do any breaking changes in master at the moment. Will switch the default in near future.