-
-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors regarding package use in Next.js + Typescript project due to module conflict #438
Comments
You can provide an example(codesandbox.io) that reproduces the error, and I'll try to fix it for you. |
Good evening. Here is the example. |
I upgraded
I may need to see what has changed in the new version of Another error may require next-transpile-modules to resolve |
I believe I have a different error. I have an error that occurs when I do saying
I have downgraded to next@12.2.6 and have used next-transpile-modules but to no avail. Reiterating, I want to use the "commands" because want to add shortcuts to the title and aria-label of the buttons (ex. Add bold text (Ctrl + B)). It seems to be an error regarding modules. I have tried replicating it again in codesandbox but it was not updating packages so I used replit instead. Please see the link below. I hope you can help with this. |
Found the solution: |
I'm using react-md-editor with next-remove-imports in a Next.js + Typescript project but getting blocked by the hordes of errors from importing the "commands" to add shortcuts to the title and aria-label of the buttons. I have read through previous issues of related errors but none seem to fix it for me. I have tried many combinations of implementation but all lead to errors such as
Error: Must use import to load ES Module:
Error: require() of ES Module
Cannot use import statement outside module
...and some others.
I have spun a replit with the error below. I tried adding "type": "module" in the package.json but it doesn't run.
https://replit.com/@alphacoma/react-md-editor-error-1
The text was updated successfully, but these errors were encountered: