Failed dynamic import should not always be cached #6768
Description
Given feedback from https://bugs.chromium.org/p/chromium/issues/detail?id=1195405#c9
In my opinion, HTML spec should also stop demanding to cache failed dynamic imports.
The rationale of this proposal is well discussed in tc39/proposal-dynamic-import#80
The ECMAScript spec has adopted the change long ago: tc39/ecma262#1645
Lack of retry-ability is stopping SPA developers from using native dynamic imports. Because they would have to reload the whole web app, only to make up for an otherwise insignificant network failure when fetching a lazy-loaded js chunk.