But it do not work:
Failed to load resource: the server responded with a status of 404 ()
17p-aea38759.js:1 TypeError: Failed to fetch dynamically imported module: https://cdn.jsdelivr.net/npm/@ionic/core/dist/ionic/p-0b5fbec3.entry.js undefined
Oe @ p-aea38759.js:1
17p-aea38759.js:1 Uncaught (in promise) TypeError: Cannot read property âisProxiedâ of undefined
at p-aea38759.js:1
p-24dc7b6e.entry.js:1 Failed to load resource: the server responded with a status of 404 ()
10p-aea38759.js:1 TypeError: Failed to fetch dynamically imported module: https://cdn.jsdelivr.net/npm/@ionic/core/dist/ionic/p-24dc7b6e.entry.js undefined
Oe @ p-aea38759.js:1
10p-aea38759.js:1 Uncaught (in promise) TypeError: Cannot read property âisProxiedâ of undefined
at p-aea38759.js:1
p-5e452afb.entry.js:1 Failed to load resource: the server responded with a status of 404 ()
2p-aea38759.js:1 TypeError: Failed to fetch dynamically imported module: https://cdn.jsdelivr.net/npm/@ionic/core/dist/ionic/p-5e452afb.entry.js undefined
Oe @ p-aea38759.js:1
2p-aea38759.js:1 Uncaught (in promise) TypeError: Cannot read property âisProxiedâ of undefined
at p-aea38759.js:1
and so on ⌠64 errors in console
Does clearing your browser cache help? Itâs possible that the chunk names (p-d9fa7c89) have changed, and your browser is trying to pull an old chunk.
It would appear that it is working now. Last Thursday it was definitely broken, however. Clearing the cache was the first thing we tried. My guess is that your CDN was in the middle of an update, temporarily breaking the link to whatever was contained in p-d9fa7c89 as it rolled out changes to itâs various server locations. This is of course speculation on my part. Whatever the case, it seems to be working seamlessly now. Thank you!
Hi @mhartington Iâm facing the same issue again today as CDN seems to be down, Please get it fixed as soon as possible thanks, and this is the error Iâm getting as below