►
Description
Lightning Talk: Node-RED Update - Nick O'Leary, Node-RED Project Lead
A
Hi,
I'm
nick
o'leary
from
the
node
red
project,
and
I
want
to
spend
just
a
few
minutes
sharing
some
of
the
things
we've
been
up
to
in
the
project
recently
and
preview.
Some
of
what
we've
got
coming
up
earlier
this
year,
we
released
the
1.3
version
of
node
red.
This
was
the
latest
milestone,
release
that
brought
a
number
of
new
features
to
both
the
node-red
editor
and
its
runtime
in
the
function.
A
For
administrators,
when
this
feature
is
enabled,
we
also
provide
allow
and
deny
list
options
to
write
some
control
over
what
end
users
are
able
to
install
the
mqtt
nodes
were
updated
to
introduce
mqtt
v5
support.
V5
brings
a
whole
host
of
new
options
to
the
protocol,
including
improved
message,
metadata
request,
response,
messaging
and
message
expiry.
A
Under
the
covers.
We've
introduced
a
new
plugins
framework
for
the
platform.
Plugins
are
a
way
to
add
additional
functionality
to
both
the
runtime
and
editor
and
will
be
how
we
deliver
some
new
features
in
the
future,
keeping
the
course
smaller
and
providing
more
choice
over
what
additional
features
a
user
has
installed.
A
With
the
1.3
release,
we
introduced
support
for
two
types
of
plugin.
First
up
are
editor
theme
plugins.
They
make
it
easier
for
users
to
install
new
themes
and
enable
them
straight
in
their
settings
file.
There's
a
great
collection
of
contributed
themes
available
at
the
node-red
contrib
themes
repository
the
second
plugin
type
are
library
source
plugins.
A
These
allow
users
to
configure
additional
libraries
that
appear
in
their
import
export
dialogs.
Within
the
editor,
we've
published
a
local
file
system
plugin
as
a
first
example.
This
allows
you
to
create
a
second
library
stored
on
your
local
disk.
You
could
point
that
as
a
shared
folder
on
dropbox,
for
example-
and
it
gives
you
a
quick
and
easy
way
to
share
flows
with
others
with
colleagues
with
whoever
you're
working
with,
and
there
are
lots
of
other
smaller
improvements
throughout
the
project,
and
you
can
find
out
lots
more
in
the
release
blog
post.
A
So
now,
let's
turn
to
what's
coming
up
with
the
release
plan
we
published
last
year.
1.3
is
the
last
milestone,
release
we'll
be
doing
in
the
1.x
stream,
which
now
goes
into
maintenance
mode,
where
only
critical
fixes
will
get
applied
and
in
its
place
is
coming
node-red
2.0,
the
main
driver
for
the
major
version
change
is
dropping
support
for
old
versions
of
node.js.
A
A
A
To
that
said,
it
was
still
quite
a
lot
of
work
to
do
and
made
me
appreciate
just
how
much
the
request
module
did
out
of
the
box
we're
fairly
confident
users
won't
spot
the
difference,
but
given
the
number
of
edge
cases
around
dealing
with
http
requests,
it
is
possible
that
something
might
slip
past
our
unit
tests
we're
also
changing
a
few
bits
of
default
behavior.
In
the
case
of
clean
new
installs
of
node-red,
for
example,
the
new
default
settings
file
hard
codes,
the
flow
file
name
to
be
flows.json.
A
A
A
A
Now,
given
the
nature
of
all
these
changes,
we'll
have
an
extended
beta
period
for
the
2.0
release,
with
the
first
beta
release
coming
later
this
month,
one
of
the
benefits
of
low-code
programming
with
tools
like
node-red.
Is
it
abstracts
away
a
lot
of
the
technical
details
of
how
things
are
working?
A
It
allows
you
to
focus
on
solving
the
problem
at
hand,
but
just
because
it's
low
code
that
doesn't
mean
you
can't
have
the
tools
you
need
to
make
high
quality
applications
and
yes
to
help
debug
when
things
aren't
going
as
they
should
to
that
end,
alongside
the
2.0
release,
we're
also
going
to
be
releasing
a
pair
of
new
tools.
That's
going
to
bring
some
new
super
powers
to
node-red
flow
developers.
A
A
Now,
when
it's
paused,
it
will
show
you
how
many
messages
are
queued
up
at
each
point.
In
the
flow
and
in
the
sidebar,
you
can
see
the
queue
of
messages
in
the
order
they
are
going
to
get
processed
each
time
you
click
the
step
button.
The
next
message
is
taken
from
the
top
of
the
queue
and
gets
processed.
A
A
The
sidebar
shows
you
the
linting
results
and
let
you
quickly
navigate
to
the
areas
of
the
flow
that
might
need
some
attention
outside
of
the
editor.
Nrlint
can
also
be
installed
and
run
as
a
command
line
tool
against
a
flow
json
file.
This
means
it
can
be
used
to
validate
flows
as
part
of
build
pipelines.
A
For
example,
some
third-party
nodes
may
want
to
introduce
guidance
about
how
their
nodes
are
used,
so
to
support
that
the
linter
rules
are
entirely
plugable,
allowing
custom
rules
to
be
created
and
shared
with
the
community
via
npm
in
wider
project
news
we're
going
to
be
launching
our
not
quite
annual
nerd
red
community
survey.
Soon,
we
last
ran
it
just
over
two
years
ago
in
2019
and
got
some
great
insights
from
the
community.
A
We've
decided
it's
time
to
rerun
it
with
some
updates.
So
if
you're,
a
node-red
user
keep
an
eye
out
for
that
when
it
launches
and
that's
everything
I
had
for
you
today-
we're
really
looking
forward
to
getting
the
node
red
2.0
beta
released
and
to
let
you
play
with
the
debugger
and
linter.
I
really
think
they're
going
to
be
hugely
useful
tools
for
the
nerdred
community.