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
import { options as n } from "https://unpkg.com/preact@latest?module";
…which results in broken code, because preact@latest currently redirects to [email protected], and that older version is not at all compatible with the upcoming Preact X hooks implementation.
So unpkg should be converting the preact import by specifying preact@^10.0.0-alpha.0 (which currently redirects to [email protected]) for that import, instead of preact@latest.
I mentioned this at #123 (comment) but filing as a separate issue since in this case the peerDependency seems to be getting ignored entirely (despite only specifying a single range).
The text was updated successfully, but these errors were encountered:
@mjackson Hmm, it may be related i.e. if the reason this is happening is because of the nested package? Otherwise it would be a separate issue related to which version it ends up picking.
Preact X's hooks module imports from "preact":
When fetching that with the ?module flag this gets converted to:
…which results in broken code, because
preact@latest
currently redirects to[email protected]
, and that older version is not at all compatible with the upcoming Preact X hooks implementation.The package.json for the hooks module specifies:
So unpkg should be converting the preact import by specifying
preact@^10.0.0-alpha.0
(which currently redirects to[email protected]
) for that import, instead ofpreact@latest
.I mentioned this at #123 (comment) but filing as a separate issue since in this case the
peerDependency
seems to be getting ignored entirely (despite only specifying a single range).The text was updated successfully, but these errors were encountered: