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
If you have a package that sets type: module, and that package imports this package you can get into a weird error state where this package seems to return a bad object. In our case, our chain was Vite --> ESBuild --> Emotion --> This package. We suspect it is this package because components that didn't rely on this rendered just fine. Components that did rely on this hit an error boundary that had the following:
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.
I'm still debugging but this library seems to be the root cause/culprit.
As an aside, is this library still under active development @felippenardi? I'm concerned that this library is not compatible with the ever changing JS ecosystem going forward
The text was updated successfully, but these errors were encountered:
I'd like to request that this package change the way it ships. If you can instead just ship transpile source code instead of prebundling this issue is basically avoided.
If you have a package that sets
type: module
, and that package imports this package you can get into a weird error state where this package seems to return a bad object. In our case, our chain was Vite --> ESBuild --> Emotion --> This package. We suspect it is this package because components that didn't rely on this rendered just fine. Components that did rely on this hit an error boundary that had the following:I'm still debugging but this library seems to be the root cause/culprit.
As an aside, is this library still under active development @felippenardi? I'm concerned that this library is not compatible with the ever changing JS ecosystem going forward
The text was updated successfully, but these errors were encountered: