-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why won't it skypack #27
Comments
as skypack is not work, see: storacha/ipfs-car#27 License: MIT Signed-off-by: Oli Evans <[email protected]>
So, I can see that skypack gets a bunch of uint8arrays and somehow one of our dependencies use the this is related to skypackjs/skypack-cdn#159 |
@olizilla I could discover that is multicodec that apparently is pulling the old Please check https://codepen.io/vascosantos/pen/mdWZmWq?editors=0011 As we can see, it only gets |
The
This is in the unixfs-importer now: https://codepen.io/vascosantos/pen/LYWwgPP?editors=0011 |
Some research happened on: https://github.com/vasco-santos/cjs-esm-skypack-build-rep And root issue updated: skypackjs/skypack-cdn#171 To unblock this, we will need to either bundle ipfs-unixfs on publish, or make it an ESM citizen |
related: web3-storage/web3.storage#220 |
trying to use skypack like:
does not work. You get a
from:
https://cdn.skypack.dev/-/[email protected]/dist=es2020,mode=imports/unoptimized/to-string.js
but there is no obvious reason why it should pull in version 2.1.3 when there is a 2.1.5 version of
unit8arrays
that does not have the problem. the older version uses TextEncoder fromweb-encoding
achingbrain/uint8arrays@v2.1.3...v2.1.5 that fails to bundle. The newere 2.1.5 doesn't. WHY IS SKYPACK USING THE OLDER BAD ONE?The text was updated successfully, but these errors were encountered: