mdx-editor v4

[rbbydotdev]

@petyosi - Is there a v4 roadmap currently planned? - Do you mind if I kick off some discussion ?

I have some breaking ideas, and there also been some tangential discussion about breaking changes (lexical peer dependency) So I will start with ....

• lexical and code editor peer dependencies
• Bring-Your-Own-Components, using something like a react context provider where you can define the components like Button, Input, Dialog. These would then be used in the plugins
• shadcn component defaults and tailwind - this could be a big lift, but the popularity of shadcn could encourage community contributions and usage of mdx-editor within the shadcn ecosystem

not required for a new version but using v4 for an epoch for new features/methodology/documentation/approach

• codesandbox base project and documentation for encouraging contributions and better troubleshooting
• cli plugin system: I've noticed many asks revolve around plugin modification, but exposing these changes in a plugin would make for a rather large surface api for said plugin. What if mdxeditor could adopt the shadcn cli approach, rather than importing the plugin you 'copy-paste' either manually or via a cli for their extension

[petyosi]

• shadcn style for the UI bits would be great. It's clearly the way to go at the moment.
• monorepo, plugins should be separate packages. Quite the work
• replacing codemirror with monaco everywhere

[rbbydotdev]

Would you like to open a v4 https://github.com/mdx-editor/editor/milestones and a V4 label ?

[jcyuan]

https://daisyui.com/compare/shadcn-vs-daisyui/