Warning: end of support for @silexlabs/grapesjs-fonts, symbols, data-source... on npm

[lexoyo]

Hi everyone,

What is concerned

The Silex GrapesJS plugins published on npm under the @silexlabs/ scope:

• @silexlabs/grapesjs-fonts (npm, repo)
• @silexlabs/grapesjs-symbols (npm, repo)
• @silexlabs/grapesjs-data-source (npm, repo)
• @silexlabs/grapesjs-advanced-selector (npm, repo)
• @silexlabs/grapesjs-filter-styles (npm, repo)
• @silexlabs/grapesjs-css-variables (npm, repo)
• @silexlabs/grapesjs-keymaps-dialog (npm, repo)
• @silexlabs/grapesjs-notifications (npm, repo)
• @silexlabs/grapesjs-storage-rate-limit (npm, repo)
• @silexlabs/grapesjs-loading (npm, repo)
• @silexlabs/grapesjs-ai-capabilities (npm, repo)
• @silexlabs/grapesjs-version-flow (npm, repo)

The impact

We stop publishing these plugins to npm. The versions on npm are now frozen at their last release: no new versions there, unless a community maintainer publishes them (see below). The published versions stay online and keep working, and we remove nothing from npm.

This is only about npm. We keep developing the plugins in the Silex monorepo: bug fixes and new features still land there, and we still welcome feature requests. So the code keeps moving, only the npm releases stop on our side.

How to contribute, and become a maintainer

As of the next Silex release, the plugins will live in the Silex (soon to be) monorepo, under grapesjs-plugins/. We keep maintaining them there. Two ways to get involved:

1. Drive the releases. Send your changes as pull requests in the monorepo. When you want a new version on npm, contact me and we publish a release. If you want to handle releases for a plugin on a regular basis, get in touch.
2. Become the owner of a plugin. If you depend on a plugin and want full control, we move it out of the monorepo into your own repository. From there it is yours: code, issues, and npm releases.

Why we are doing this

Running separate releases for every plugin had become too complex to keep up. Silex also has a NLnet grant: I am working full time on it for six months, with parallel branches and versions on the core. Keeping a release pipeline for each plugin on top of that is not realistic, and these plugins are used widely outside Silex anyway, so they are better maintained by the people who use them.

How do you see it? Tell us in the comments.