Latest version is not on npm
It might happen to see a new build available in the dev repository but that means the version is not yet stable to be published 😉
Read full answer below ↓Question
I see that the version numbers are incremented, but the package is not published on npm after 0.15.15. Time for a 0.16 😃 Other issue about npm: https://github.com/artf/grapesjs/issues/2568 (not sure if related)
Answers (1)
It might happen to see a new build available in the dev repository but that means the version is not yet stable to be published 😉
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3778
Select options are not displaying - new anomaly
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? ChromeReproducible demo link https://github....
Issue #1051
[BUG] CommandAbstract's callRun and callStop should return result for backward compatibility
Hi @artf, after the latest upgrade (0.14.9) some of my commands that rely on the results of other commands fail. This happens because of th...
Issue #3404
Style Manager Issue.
Hi @artf I want to hide and show style properties for specific component. After referencing this issue https://github.com/artf/grapesjs/iss...
Issue #980
[BUG] Related with task https://github.com/artf/grapesjs/issues/873
Hello, After restoring editor from db still have some part of bug present. It seems inside of script: function () traits will have old valu...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.
Browse premium plugins →Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.