Runtime error when using an external react module about preact HOT 5 CLOSED

The module is linked externally using npm link. When I copy the external module inside the project, then there is no such problem.

Don't use npm link, it's very broken (by design, it seems) when it comes to module resolution. Use something like yalc instead.

There isn't any chance of multiple copies of preact because I am not using any other modules that use preact.

This isn't quite how it works.

What's happening is your lib is pulling a copy of Preact through the symlink and your local application also has one, ergo, two copies.

Edit: Related #4331 (reply in thread)

from preact.

Yeah it's 99% an issue with the build tooling used. The error occurs when there are multiple Preact versions used.

from preact.

Why does it work with React?

from preact.

React's internals might be a bit more forgiving here? Not entirely sure to be honest, I don't work with React much, sorry.

You could also be running up against the dual-package hazard potentially, as React still doesn't ship ESM. Depends on how you're building your package.

from preact.

Going to close this on out as it's hopefully been addressed.

Feel free to reply if you're still having issues and we can take a look.

from preact.