-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
6.4.0
breaks dynamic import from some CDNs
#4077
Comments
This is very similar to #4071 but in a different context. Not sure if this deserves its own issue, feel free to close this issue if it's redundant. |
Hmmm. The CDN should be pulling in the file from the But I’ll get these upstream changes submitted tomorrow so I can switch back to using the official package… |
Same issue here |
Same issue when using npm verb exit 1 |
This is the same issue as #4071, I'll be keeping that issue updated instead of this one. :) |
This should be fixed in v6.4.2. Can you try it out and let me know if you still have any problems? |
Thank you for the update! I just tried this: const ethers = await import('https://cdn.jsdelivr.net/npm/[email protected]/+esm'); And looks like it's working now. Thanks! |
Awesome! Glad to hear it! Thanks. :) |
Ethers Version
6.4.0
Search Terms
cdn, 6.4.0, jsdelivr
Describe the Problem
Steps to reproduce the issue:
jsdelivr
CDN:Expected result: ethers is imported successfully.
Actual result: the import fails when trying to import the
ens-normalize
dependency:Workaround:
cdnjs
, works as expected:I believe the root cause is in 7e272a3, where
package.json
was updated like so:Since other CDNs handle this dependency correctly, it may just be an issue with jsdelivr and nothing to do with ethers. Nonetheless, thought others may want to know in case they encounter this very specific edge case.
Code Snippet
No response
Contract ABI
No response
Errors
No response
Environment
Browser (Chrome, Safari, etc)
Environment (Other)
No response
The text was updated successfully, but these errors were encountered: