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
[vite] Internal server error: Directory import '<repo path>/node_modules/.pnpm/@[email protected]_@[email protected]_@[email protected][email protected]__@emotion+style_n4nk7wpf5mrcjlykwo4hytjbzm/node_modules/@mui/material/Box' is not supported resolving ES modules imported from <repo path>/node_modules/.pnpm/@[email protected]_@[email protected]_@[email protected][email protected]__@emotion+style_n4nk7wpf5mrcjlykwo4hytjbzm/node_modules/@refinedev/mui/dist/index.mjs
Did you mean to import "@mui/material/node/Box/index.js"?
at finalizeResolution (node:internal/modules/esm/resolve:259:11)
at moduleResolve (node:internal/modules/esm/resolve:933:10)
at defaultResolve (node:internal/modules/esm/resolve:1157:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:390:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:359:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:234:38)
at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39)
at link (node:internal/modules/esm/module_job:86:36)
Steps To Reproduce
create remix-spa app by pnpx create-remix@latest --template remix-run/remix/templates/spa
In Remix projects using @refinedev/mui you may encounter issues due to ESM issues from Material UI packages, please refer to this issue if you have any problems related to this: mui/material-ui#39765
https://github.com/mui/material-ui/issues/39765
Describe the bug
I create a remix-spa app by
pnpx create-remix@latest --template remix-run/remix/templates/spa
Then, I add some refine components to
root.tsx
it raise an error
Steps To Reproduce
pnpx create-remix@latest --template remix-run/remix/templates/spa
@refinedev/core
,@refinedev/mui
,@mui/material
@refinedev/mui
Expected behavior
no error
Packages
Additional Context
No response
The text was updated successfully, but these errors were encountered: