Skip to content

Discussion: Open to extract the core into a separate package? #77

@Cruiser13

Description

@Cruiser13

Thank you for creating this library! I think it is really useful.
We mainly build apps with Vue.js in our company. While we can use the editor in a vue.js environment with a react bridge, the overhead with shipping react side-by-side with vue is quite huge.
So we are thinking about forking the package and build a vue version of it.

But at the moment the core and the gui are very tightly bundled. So we would definately break any upstream options here. Roughly 60-70% of the code (for OOXML parsing, document model, layout engine, ProseMirror schema/plugins/commands) are framework agnostic as far as I can see though.

Would you be open for PRs to extract that core into a separate - framework agnostic - package that could be used for the current version and the vue variant? That way any of our contributions for the vue package could be directly used in the react repository aswell.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions