FlowDrop 1.3.0: Take Control of Your Node Ports
FlowDrop 1.3.0 gives you full control over how ports appear on your workflow nodes — reorder them, hide specific ones, and trust that every port is visible by default.
FlowDrop 1.3.0 is out, and it brings a long-requested capability: full control over the ports displayed on your workflow nodes.
The problem
When you define a node type with multiple input and output ports, FlowDrop used to make an opinionated choice about which ones to show. Users would see a limited subset of ports, and there was no clean way to surface all of them or decide the order they appeared in.
This made it harder to build node-heavy workflows where port layout actually matters — especially when different ports represent different data types or execution paths that users need to reason about visually.
What’s new in 1.3.0
Every port is visible by default
Nodes now show all of their defined ports out of the box. No more hidden ports that users have to discover through configuration — what you define is what gets displayed.
Reorder ports to match your domain
You can now specify a portOrder on any node to control exactly how ports are arranged. If you have a node with five outputs and the most important one is buried at the bottom, you can bring it to the top. The order in your workflow editor can now match the mental model your users already have.
Hide specific ports when they’re not relevant
Some ports only make sense in certain contexts. With hiddenPorts, you can suppress individual ports by ID without affecting the rest. Combined with the existing “hide unconnected ports” option, you now have layered control: hide by default, reveal on connect, or hide specific ones permanently regardless of connection state.
Why it matters
Workflow editors live and die by how quickly users can understand what a node does at a glance. Port layout is a big part of that — it communicates data flow, execution order, and the relationship between inputs and outputs.
With 1.3.0, the people building the node types are in control of that communication again.
Upgrading
npm install @flowdrop/flowdrop@1.3.0No breaking changes. Existing nodes continue to work — they’ll just show all their ports now instead of a subset.