There seems to be a strange hit-and-miss with standalone babel versions even across patch numbers.
(e.g. I don't think its the contents of the package causing the failure)
https://cdn.skypack.dev/@babel/standalone@v7.11.0 took a long time then ✅
https://cdn.skypack.dev/@babel/standalone@v7.11.9 took a long time then ❌
Babel standalone is massive; probably one of the largest npm packages in existence. So it seems like behavior below indicates either
running out of memory and crashing
or maybe the backend is fine and its just so long to build that the on-demand build times-out.
The first time I loaded v7.13.7 (and many other others) it seems not to be cached and I get this:
(possibly crashing the backend)
After reloading, then I get a cached error message (for v7.13.7 and all the others that seem to timeout):
/*
* [Package Error] "@babel/standalone@v7.13.7" could not be built.
*
* No build output found.
*
* How to fix:
* - If you believe this to be an error in Skypack, file an issue here: https://github.com/skypackjs/skypack-cdn/issues
* - If you believe this to be an issue in the package, share this URL with the package authors to help them debug & fix.
* - Use https://skypack.dev/ to find a web-friendly alternative to find another package.
*/
console.warn("[Package Error] \"@babel/standalone@v7.13.7\" could not be built. ");
throw new Error("[Package Error] \"@babel/standalone@v7.13.7\" could not be built. ");
export default null;
Behavior
There seems to be a strange hit-and-miss with standalone babel versions even across patch numbers. (e.g. I don't think its the contents of the package causing the failure)
https://cdn.skypack.dev/@babel/standalone@v7.11.0
took a long time then ✅https://cdn.skypack.dev/@babel/standalone@v7.11.9
took a long time then ❌https://cdn.skypack.dev/@babel/standalone@v7.12.15
✅https://cdn.skypack.dev/@babel/standalone@v7.12.16
✅https://cdn.skypack.dev/@babel/standalone@v7.12.17
took a long time then ✅https://cdn.skypack.dev/@babel/standalone@v7.12.18
took a long time then ✅https://cdn.skypack.dev/@babel/standalone@v7.12.19
took a long time then ❌(there is no 7.12.19 but it doesnt give the normal missing-version-error)
https://cdn.skypack.dev/@babel/standalone@v7.13.7
took a long time then ❌https://cdn.skypack.dev/@babel/standalone@v7.13.8
took a long time then ✅https://cdn.skypack.dev/@babel/standalone@v7.13.10
took a long time then ❌https://cdn.skypack.dev/@babel/standalone@v7.15.0
✅https://cdn.skypack.dev/@babel/standalone@v7.15.1
took a long time then ❌https://cdn.skypack.dev/@babel/standalone@v7.17.8
❌ (latest)Babel standalone is massive; probably one of the largest npm packages in existence. So it seems like behavior below indicates either
The first time I loaded v7.13.7 (and many other others) it seems not to be cached and I get this: (possibly crashing the backend)
After reloading, then I get a cached error message (for v7.13.7 and all the others that seem to timeout):