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
What you did: Upgraded mdx-bundler on a remix.run project
What happened:
Building Remix app for production...
Error: Could not resolve './dirname-messed-up.cjs' from ./dirname-messed-up.cjs?commonjs-external
at error (<redacted-repo dir>/node_modules/rollup/dist/shared/rollup.js:5305:30)
at ModuleLoader.handleResolveId (<redacted-repo dir>/node_modules/rollup/dist/shared/rollup.js:18531:24)
at <redacted-repo dir>/node_modules/rollup/dist/shared/rollup.js:18487:22
at async Promise.all (index 0)
at async ModuleLoader.fetchStaticDependencies (<redacted-repo dir>/node_modules/rollup/dist/shared/rollup.js:18485:34)
at async Promise.all (index 0)
at async ModuleLoader.fetchModule (<redacted-repo dir>/node_modules/rollup/dist/shared/rollup.js:18461:9)
at async Promise.all (index 10)
at async ModuleLoader.fetchStaticDependencies (<redacted-repo dir>/node_modules/rollup/dist/shared/rollup.js:18485:34)
at async Promise.all (index 0)
Problem description: Something might be wrong in the implementation of #21
Suggested solution: Unfortunately I don't have a lot of background to suggest a solution. Thought about reporting given that the error seems related to #21 which was just released.
The text was updated successfully, but these errors were encountered:
Bummer. I think this is such a one-off thing that we can just hack this to make it work. We're doing some wonky things in this repo thanks to the native ESM mix of our deps and current lack of support from tools.
Luckily, I see this project as mostly "done" so I'm not worried about the long-term maintainability of these workarounds 😅
mdx-bundler
version: 3.2.0node
version: 14.16npm
version: 6.14.11What you did: Upgraded mdx-bundler on a remix.run project
What happened:
Problem description: Something might be wrong in the implementation of #21
Suggested solution: Unfortunately I don't have a lot of background to suggest a solution. Thought about reporting given that the error seems related to #21 which was just released.
The text was updated successfully, but these errors were encountered: