Changes

Headless CMS
anchor

Removed Unnecessary Variables Passed Into Storage Operations (#2403external link)
anchor

We removed latestEntry and latestStorageEntry from being passed into the storage operations because they are not required for storage operations to function. These objects were used for debugging purposes only. While using storage operations programmatically, we realized that it’s confusing, and causes unnecessary friction while developing plugins, so these are now gone.

Improve Rich Text Editor Menu Positioning (#2419external link)
anchor

We gave some love to our RichTextEditor component, and polished out the menu positioning and visibility. The underlying editorjsexternal link is now also upgraded to the latest version, so you’ll notice a nicer layout of tools in the menu.

Rich Text Editor ToolsRich Text Editor Tools
(click to enlarge)

Development
anchor

Require Node >=14 to Create a Webiny Project (#2420external link)
anchor

Until now, we were very strict about what versions of Node you can use to create a new Webiny project. Starting with this release, we made the requirement less strict, and we now allow you to create new projects with any version of Node that is >=14. This means, 14, 15, 16, etc. Node 12 is no longer supported, as we’re using some newer Node features, and to be able to enjoy the new stuff, we need to stop supporting older versions of Node.

To understand our support of Node versions better, take a look at this official diagramexternal link:

Node ReleasesNode Releases
(click to enlarge)

We’ll try to follow Node’s lifecycles, as that’s what the rest of the ecosystem is doing, and we’ll be primarily focusing on supporting LTS releases. If unstable (odd release numbers like 15, 17, etc.) releases work for you, that’s great! Do let us know that they work for you on our Community Slackexternal link, but the core team will be mainly focusing on supporting LTS versions.