🚀 Major Refactors Coming: Plugins as Separate NPM Packages

[mayank1513]

Hey everyone! 👋

We're planning a major refactor in how we handle plugins in mdast2docx. The goal is to improve compatibility and ease of use across different environments.

🔥 What's Changing?

Currently, all plugins are exported from a single plugins/index.ts file. However, this creates issues:

• Node.js plugins throw errors when used in client-side applications.
• Client-side plugins break in Node.js environments.
• A workaround is using separate export files (common.ts, node.ts, and client.ts), but this complicates usage.

🛠 Solution

We plan to export each plugin as a separate NPM package to provide a uniform, environment-agnostic way of using them.

💡 Looking for Feedback

Would love to hear your thoughts! Do you see any potential issues, or have suggestions for alternative approaches?