The first beta release of Node-RED 2.2.0 is now available.
There are not a lot of new features in this release, but here are the highlights.
The Change Log has the full list of changes.
Note: if any issues are reported against the beta, we'll update this post to list them here. If you hit a problem, please do check back here before adding a comment.
- Copy Text actions broken for non https/localhost domains
The main search dialog now keeps a history of your searches. This makes it easy to repeatedly search for the same thing.
With snap-to-grid enabled, nodes with hidden labels (eg link nodes) can now be aligned on either their left or right edge. This will make it easier to get everything to line up.
There is another pull-request from @dceejay that will help with some alignment woes with non-grid sizes - but I'm still thinking about if that's quite the right approach. Either way, we'll have more for the final 2.2.0 release.
You can now delete a node from the middle of a flow and have the wiring automatically repair itself in the background:
This is done by holding the Ctrl (or Cmd) key when you press delete.
You can also detach a node from the flow without deleting it:
We haven't assigned a default shortcut for that, but you can assign one yourself in the Keyboard pane of the Settings dialog. The action is called
You can also select multiple wires by ctrl-clicking on them.
When you select multiple nodes, we also highlight any wires between them. This can make it easier to follow a flow once you have selected it.
Finally, we've added the ability to remove wires by slicing through them. You do this by holding the ctrl (or cmd) key, then dragging the mouse with the right-hand button pressed:
- The JSON node will now attempt to parse Buffer objects if they contain a valid string
- The TCP Client nodes support TLS connections
- The WebSocket client node now lets you specify a sub-protocol to connect with
Be sure to read through the Change Log to see what else is in there.
If you want to try out the beta, you will need specify node-red@next when you use npm to update. Without the
@next you'll still get 2.1.x
So on a Pi you'd do:
sudo npm install -g --unsafe-perm node-red@next
If you hit any problems, please report them either as a reply on this topic, or in the #core-dev slack channel. Please do not post new topics to the forum regarding the beta as that could confuse users who are not using the beta.
There are a couple more PRs being considered for 2.2.0 - you can see the backlog here (although nothing is guaranteed until it is merged and released...)
The goal is to release 2.2.0 at the end of this month.