You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the link above, you can see that nothing is rendered on the page.
The error message that I get is a 404 on https://unpkg.com/[email protected]/devtools?module.
I believe this is because of trying to use scope like naming without scoping. So preact/devtools instead of @preact/devtools. unpkg is picking this up as a path name instead and not reading from the package.json.
Expected Behavior
https://unpkg.com/preact/devtools should resolve to https://unpkg.com/[email protected]/devtools/dist/devtools.module.js?module
Actual Behavior
https://unpkg.com/preact/devtools resolves to https://unpkg.com/[email protected]/devtools?module
The text was updated successfully, but these errors were encountered:
The recommended solution is to use a CDN which supports proper module resolution, like https://npm.reversehttp.com/
// preact and preact/hooks: 10.5.7, and htm/preact: 3.x.x:import{html,render}from'npm.reversehttp.com/[email protected],[email protected]/hooks,htm@3/preact';
Closing, because this is a duplicate of #2564 and we can't solve it on our end.
Reproduction
https://codesandbox.io/s/preactdebug-esm-7165v?file=/index.html
Steps to reproduce
Using the link above, you can see that nothing is rendered on the page.
The error message that I get is a 404 on
https://unpkg.com/[email protected]/devtools?module
.I believe this is because of trying to use scope like naming without scoping. So preact/devtools instead of @preact/devtools. unpkg is picking this up as a path name instead and not reading from the package.json.
Expected Behavior
https://unpkg.com/preact/devtools
should resolve tohttps://unpkg.com/[email protected]/devtools/dist/devtools.module.js?module
Actual Behavior
https://unpkg.com/preact/devtools
resolves tohttps://unpkg.com/[email protected]/devtools?module
The text was updated successfully, but these errors were encountered: