not ES module

[nikitapilgrim]

✖ dependency "react" has no ES "module" entrypoint.
Its fixable?

[FredKSchott]

Not until React ships a "module" ESM build. Until then, replace all imports of "react" with an ESM-flavored build like "es-react"

It may even be worth adding a react-specific error to our console log given how common this probably is

[nikitapilgrim]

But i can use wrapper for import, export for non ES module and then use in pika custom path dependencies to wrapper? If possible, how to specify the custom path in pika?

[FredKSchott]

you know, it would be very interesting if we could support custom wrappers. This would give us CJS support, but also allow you to use a customer wrapper of only the exports you wanted, which would allow @pika/web to tree-shake out the rest.

[FredKSchott]

Support for common.js dependencies has been added, and we now have a workaround for using React: https://github.com/pikapkg/web#a-note-on-react

Hope that helps!