-
-
Notifications
You must be signed in to change notification settings - Fork 613
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
tree shaking #326
Comments
We have a package for the core https://www.npmjs.com/package/@udecode/slate-plugins-core I'm a bit stuck on packaging all the other plugins as it looks like, in development/test (storybook, jest), I need to build the dependencies (like slate-plugins-core) on each change and that's quite annoying...Still looking for a solution. You can let me know which plugins you would like as package. |
ok got it can pipe be moved to core? just because its pretty convenient if you're using this package. const editor = useMemo(() => pipe(createEditor(), ...(withPlugins ?? [])), [
withPlugins,
]); |
Will do! |
feel free to close this if you'd like. I consider my original issue resolved! |
I'm also looking forward to this. The build is a bit big right now and includes packages that I'm not using like all the ui libraries. (fabric, tippy, prism). |
See #363 |
Is it possible to enable tree shaking in this project? Alternatively could the core be imported separately from the rest of the prebuilt plugins. I want to use the core because the plugin api is so much more extensible compared to the api offered by slate but I have to import some large dependencies which I'm not using such as remark.
The text was updated successfully, but these errors were encountered: