►
From YouTube: Looking at the Future of Express: Using and Contributing to Express in 2020 - Wes Todd, Netflix
Description
Speakers: Wes Todd
Express is one of the most influential and important projects in the Node.js ecosystem. In this talk, Wes will share his journey going from a user to a contributor and ultimately to a Technical Committee member. He will share what he learned along the way and share these lessons to help you to better understand how to get involved.
Did you know that "Express" is more than a single module? Wes will introduce the different modules which make up "Express", sharing some of the surprising ways people use these modules outside of Express itself.
Finally, he will touch on what is upcoming in Express 5 & 6, and ways you or your company can use and support the project in the upcoming year.
A
So
welcome
everyone
in
my
pocket.
Sorry
getting
set
up
a
little
bit
during
the
time
we're
running
late
in
this
room.
I
guess
so
welcome.
I'm
Wes,
I
work
at
Netflix
but,
more
importantly,
I,
have
the
immense
pleasure
to
work
on
a
lot
of
open
source
JavaScript
all
right.
So
that's
probably
what
you're
all
here
today
to
talk
about
right.
You
don't
really
care
about
what
I
do
at
work.
You
wanna
know
about
Express
right,
yeah,
some
feedback.
Here
there
we
go
okay,
much
better,
much,
much
better,
okay,
so
to
get
started.
A
So
does
anybody
in
the
room
use
fast
if
I
yeah
yeah
yeah
a
couple,
not
very
many
Wow,
okay,
I
thought
more
people
would.
Would
you
specify
it's
a
great
HTTP
web
framework
so
when
I
first
got
introduced
to
FASTA,
Phi
I
did
what
I
often
do,
which
you
know
call
me
crazy,
but
I,
cracked,
open
the
package.
Jason
and
I
started
pouring
through
its
dependencies.
You
know
I'm
a
read
the
source
code,
kind
of
person,
so
I
was
in
there
and
I
I
noticed
one
that
I
recognized
the
module
proxy
adder.
A
Does
anybody
familiar
with
what
that
one
does?
No,
no!
No
one
man
I'm
given
stumpers,
so
proxy
adder
is
a
module
that
will
find
the
client
IP
address
from
the
x-forwarded-for
header
right,
so
y'all
work
on
the
internet.
You
know
you
cannot
trust
users
on
the
Internet.
Everyone
lies
right,
so
headers
come
from
a
user,
can't
trust
them.
So
proxy
adder
goes
through
the
process
of
safely
parsing,
the
x-forwarded-for
header,
so
that
your
application
can
get
an
IP
address
that
it
trusts
right.
So
fast,
sorry,
I,
haven't
talked
too
much
yet
this
morning.
So
fast.
A
If
I
use,
is
this
module
to
get
a
trusted?
Ip
address
it
parses
the
list
loops
through
them
finds
the
first
untrusted
IP
address,
which
means,
if
you
water,
that's
the
key
okay.
So
if
you've
configured
your
servers
correctly,
which
obviously
you
all
have
because
you're
all
stellar
engineers
right,
then
you
have
put
in
all
of
your
on
network
IP
addresses.
So,
as
the
proxies
you
know,
the
request
is
proxied
through
your
infrastructure
when
it
gets
to
your
node
server,
it
might
have
three
or
four
different
IP
addresses
in
there.
A
So
this
is
one
really
great
example
of
the
way
that
the
Express
modules
are
used
in
the
ecosystem,
but
there's
a
ton
of
other
ones.
Does
anybody
use
react?
Router?
Yes,
a
lot
more?
Okay,
there
we
go
your
friend
and
people.
Aren't
you
so
react.
Router
uses
path
to
reg
X
under
the
hood
for
its
route,
parsing
path,
the
regex,
anybody
guess
who
maintains
that
express
team?
Yes,
of
course,.
A
What
about
web
pack
right?
Probably
everybody
if
you're
using
richt
router
as
well
web
pack,
dev
server,
that's
express!
Also,
though,
as
a
as
you
can
see,
web
pack
has
quite
the
dependency
tree,
so
in
there
you
will
find
Express
and
everything
that
is
directly
required
as
a
dependency
or
terms
of
dependency
of
Express.
But
you
also
find
that
serve
index
compression
and
range
parser
are
in
there
independently
right.
So
the
reach
of
these
modules
that
make
up
the
that
are
under
the
umbrella
of
Express.
A
They
go
into
all
of
these
little
areas
that
it
takes
to
run
an
HTTP
server,
so
view
anybody
use
view
yeah
view.
Okay,
do
you
use
it
with
next?
Next
same
kind
of
thing,
their
server
uses,
compression
etag
fresh
on
header,
serve
static,
all
Express
modules,
it
also
uses
connect,
which
you
could
say
is
an
express
module
right.
It's
like
the
precursor,
though,
and
lastly,
anybody
fan
of
Zeit
products.
They
make
a
lot
of
great
stuff,
yeah.
A
You'd
only
be
partially
right.
This
person,
you
all
know
who
Doug
Wilson,
is
know
yeah
some
people
he's
not
a
bird.
You
will
see.
He
is
some
other
inanimate
objects,
we'll
see
in
a
second,
so
Doug
back
in
2013
was
participating
in
the
project.
You
all
probably
are
like
oh
yeah
TJ
right.
What
about
TJ
well,
TJ
famously
left
the
note
ecosystem
around
then,
and
a
bunch
of
other
people
stepped
in
to
help
foster
the
project
very
quickly.
A
It
became
clear
that
Doug
was
both
the
most
prolific
and
the
only
one
who
was
going
to
stick
around
effectively
a
lot
of
other
people,
sort
of
moved
on
to
other
things.
Kind
of
like
TJ
did
so
slowly.
Doug
became
the
most
prolific
maintainer
in
open
source
would
be
my
guess.
One
of
the
most
this
is
a
few
years
of
his
github
graph.
I
went
through,
and
then
you
might
see
a
couple
of
gray
spots
there
and,
like
I,
think
this
is
like
2014
to
2019
14
15,
16,
17,
18,
19,
right
very,
very
prolific.
A
So
this
is
mostly
Express,
and
if
you
look
at
this
you're,
probably
thinking
how
could
he
possibly
do
this?
He
has
a
full-time
job
right.
I
said
the
same
thing
in
2013.
Well,
I
guess
maybe
was
2014
and
and
I
was
looking
at
the
project
I'm
going
wow
like
all
the
all
these
maintainer
czar
started.
Moving
on
to
other
things,
Doug
is
very
committed,
but
also
isn't
gonna
burn
out
right
like
that's.
This
is
a
lot
of
work
right.
A
So
let's
talk
about
myself
and
when
I
got
into
the
project.
So
around
time
it
was
2014.
I
was
a
user.
You
know,
hopefully,
like
all
of
you
are
I,
didn't
ask
who
uses
Express
I'm,
just
assuming
that
you
all
do
and
I
was
looking
at
the
project
just
lightly
following
the
github.
You
know
just
I
wasn't
super
involved,
but
my
company
was
our
entire
app
stack
was
built
on
top
of
Express
right.
We
had
a
hundred
micro
services,
all
of
them
Express
and
so
I
said.
A
Then
Netflix
always
actually
added
this
slide
only
because
I
was
getting
really
annoyed.
With
this
thing
repeating
over
and
over
as
I
was
working
on.
My
slides
and
I'm
like
something
I
gotta
I
gotta
have
something
in
the
middle
there
to
break
it
up.
I'm
skipping
ahead,
okay,
so
where's,
my
potato,
there's
my
potato
so
I'm
getting
into
the
project
and
for
a
few
days
the
primary
maintainer
of
Express
was
a
potato.
A
He
change
his
profile
picture.
He
changed
his
name
and
it
is
you
can't
guess
potatoes,
don't
type
very
well
right,
so
also
no
commits
no
work
being
done
right.
It
happened.
The
thing
I
was
worried
about
happened.
Right
was
the
primary
maintainer
was
like
I
can't
deal
with
some
of
this
stuff
right,
there's
a
lot
of
work,
so
that
was
when
I
decided
that
I
was
going
to
jump
in
on
the
project.
So
I
opened
up.
My
oh
I
think
I
got
a
missing
slide
here.
A
Well,
I
opened
up
my
first
issue
and
it
was
talking
about
the
the
router
being
published
as
a
separate
module
and
it
turned
out
that
that
aligned
really
well
with
what
the
the
team
was
was
thinking
about
for
this.
So
within,
like
two
months,
the
first
commit
was
made
on
the
pillar,
jeaious
router
module,
which
will
be
the
is
and
will
be,
the
router
for
Express
v5.
A
This
was
in
2014,
so
it's
been
hanging
there
for
quite
a
while
I
did
that
I
started
working
on
triaging
a
few
issues
then-
and
this
is
where
I
get
to
this
I
made
my
first
real
code
contribution.
So
this
was
a
silly
little
thing.
As
you
can
see
here,
it's
a
single
index
file
license
readme,
nothing
out
right.
This
is
a
polyfill,
because
at
the
time
I
was
running
the
Express
router
in
the
browser
in
ie8.
Okay,
so
we
needed
a
polyfill
for
this
I
did
it
today.
This
gets
about
seventeen
point.
A
Two
million
downloads
a
week
stupid
little
line
of
code
right,
tiny
contribution,
outsized
impact
on
the
community.
You
don't
even
need
this
anymore.
It
still
ships
with
it,
like
I,
said
seventeen
million.
No,
you
shouldn't
use
this
anymore.
There's
you
know,
we've
moved
past
this.
We
have
object
out,
set
prototype
of
right,
but
back
then
we
didn't
right.
A
So
we
needed
something
that
was
my
first
code
contribution
and
I
show
that,
because
the
impact
is
huge,
so
this
is
a
little
graph
just
comparing,
and
this
is
downloads
per
day,
the
project
and
all
of
the
other
people
in
the
ecosystem
right.
This
is
a
outsized
impact
for
the
code
that
we
support
right
as
an
express
team.
A
So
when
I
was
doing
this
I,
you
know
I
work
at
Netflix
now,
so
it's
a
little
bit
different,
but
back
then
the
code
that
I
wrote
could
reach
like
a
couple
thousand
people
right
like
the
work
I
was
doing.
It
was
a
startup.
We
had
you
know
a
small
user
base
when
I
realized
the
impact
that
I
could
have
on
people
via
the
Express
project
and
the
code
that
we
were
shipping
with
that
project.
It
really
blew
my
mind.
A
It
made
me
like
I,
like
open
my
eyes
to
what
open
source
impact
really
looks
like
right,
and
this
is
today
I
think
the
Downloads
were
probably
lower
back
then,
because
javascript
is
growing
and
that
means
Express
is
growing,
but
but
still
it
felt
like
really
powerful
right,
like
I.
Have
these
tools
and
I
made
these
like
this?
This
module
was
like
a
couple
lines.
Right
took
me
less
than
an
hour
to
write
and
and
was
reaching
you
know
now.
My
code
is
now
running
on
on
millions
and
millions
of
people's
projects.
A
So,
as
I
went
from
there,
you
know
sort
of
typical
stories.
You
slowly
get
more
and
more
involved
in
the
project
and
I
today
and
one
of
the
I'm,
the
second
most
prolific
contributor
way
behind
Doug
right.
But
if
you
look
at
it,
it
quite
quickly
drops
off
so
you'll,
see.
Linus
and
Blake
are
both
TC
members
as
well.
There's
a
couple
people
who
just
these
contributions
is
code
and
comments
and
other
sort
of
github
activity.
A
Not
much
has
changed
in
the
past
few
years,
so
in
2018
I
made
the
argument
that
this
was
a
good
thing
right
and
and
I
still
believe
that
it
is
because
the
power
of
Express
and
the
ecosystem
is
that
it
is
stable,
and
you
know
you
can
build
on
top
of
it
and
run
a
service
for
the
next
and
we're
talking
Express
for
lon
landing
in
like
2013,
and
it's
still
the
primary
major
version
right.
You
can
run
a
service
on
top
of
Express
without
a
lot
of
churn.
It
will
be
stable.
A
So
I
was
looking
at
it
going.
What
can
I
do
you
know
to
push
this
project
forward?
I
had
all
these
open,
PRS
I
had
a
lot
invested
in
in
being
maintainer
of
Express,
but
I
was
looking
at
some
of
the
the
movement
on
the
project
and
I
was
like
this
is
a
little
slower
than
I
would
like,
and
I
will
not
become
a
potato
I.
Don't
have
time
for
that
right,
like
I've
got
a
job
too
I'm
not
like
Doug
is
amazing
right,
but
I
have
a
daughter.
This
is
my
life
I'm.
A
That
is
more
important
right
to
me,
then
Express,
so
I'm.
Looking
at
this
going,
how
and
I
helped
solve
this
problem
and
I
learned
a
lot
about
so
I'm
a
recent
father
and
through
having
a
daughter,
I
I,
really
saw
this
parallel
with
raising
a
child
and
having
an
open-source
project
right.
So
it's
a
little
silly
at
you
know
at
first
you're
like
oh
so
they're
cute
I
have
this
little
baby
I
get
to
take
care
of,
and
and
then
you
realize,
like
really
it's
a
person
right.
A
Open-Source
is
just
a
bunch
of
people
write
the
code
sure,
but
what
matters
is
the
community
and
the
people
behind
it
right?
So
I
people
are
squishy.
We
have
all
these
sort
of
weird
things:
we're
trying
to
solve
some
hard
problems
in
in
our
software
right,
but
really
I
want
to
challenge
everybody
to
think
about
the
hardest
problem
in
all
of
this
is
a
squishy
humans
right,
our
little
babies
and
and
the
people
who
they
will
become
right.
A
That
is
really
the
hard
problem,
so
the
project
I
really
want
to
focus,
and
this
is
where
we're
going.
Finally,
it's
how
many
minutes
in
halfway
through
the
talk
and
I
finally
get
to
the
title
slide
so
looking
to
the
future
of
Express
the
next
decade.
What
I
want
it
to
be
about
is
community
building
right
I
want
to
have
open
governance
models.
I
want
to
have
a
nice
onboarding
experience
for
new
contributors.
A
I
don't
want
that
drop
off
from
176
to
76
to
22,
and
that
person
is
just
a
drive
by
on
a
PR
right.
I
want
to
see
project
growth
I
want
to
see
a
community
that
we
can
rebuild
right,
that
existed
back
in
2012
and
2013
when
node
was
exciting
and
new
right,
but
now
we
have
apps
to
maintain.
We
have
people
who
depend
on
our
code
to
run
their
products
right,
so
to
do
that,
I
want
to
spend
the
next
atleast
year
really
focusing
on
you
all
right,
like
you're.
A
A
So
sorry,
if
I'm
disappointing
you
in
that,
but
I
that
you
know,
we
all
focus
so
much
on
that
that
we
can
very
easily
lose
sight
of
the
impact
of
our
work
and
the
ways
that
getting
involved
really
matters.
I
I
was
laughing
at
you
know:
I
I'm,
not
a
huge
fan
of
the
one
plus
one
equals
three
from
the
keynote
before,
but
I
think
the
sentiment
is
really
what
I
I
want
to
spend.
A
The
rest
of
the
time
talking
about
right
is
how
we,
as
a
community
and
as
a
team
who
use
and
love
some
of
these.
You
know
JavaScript
projects
can
come
together
and
and
exponentially
impact
the
the
community
so
and
the
project.
So
there
will
be
some
code
involved
in
that
right.
It's
not
just
a
bunch
of
comments
in
github,
so
we
have
this.
If
you
can
see
here
for
2014
was
when
the
Express
5pr
was
opened
right.
So
we
have
a
lot
of
code
that
needs
to
be
committed
and
and
push
to
the
project.
A
What
we've
done
as
the
Technical
Committee
is,
we've
decided
that
express
five
needs
to
be
cut.
We
need
to.
We
need
to
push
that
release
right.
So
a
lot
of
the
things
on
this.
This
original
list
are
probably
not
going
to
make
it
into
the
Express
five
release.
So
here's
where
the
the
technical
parts
do
come
in,
we
will
be
shipping
promised
sketch
support,
which
I
think
is
probably
the
single
biggest
thing
that
people
care
about
I
hope
in
this
room,
HTT
be
fought
to
was
on
this
list
and
it
is
being
dropped.
A
A
Try
to
hold
me
to
it
and,
and
then
from
there
on
you
know,
the
breaking
changes
will
have
happened
and
we
will
have
the
path
forward
for
all
of
you
to
contribute
to
the
project
and
have
it
really
move
fast
and
and
for
you
to
feel
the
impact
of
your
work.
So
to
do
that,
let's
now
talk
about
some
of
the
community
things
that
we're
going
to
be
doing
so.
A
We've
been
working
a
lot
with
the
package
maintenance
working
group,
which
is
a
node
core
working
group
and
we've
been
talking
about
how
we
can
build
programs
that
help
these
projects
like
Express,
but
not
limited
to
support
the
work.
So
one
of
the
first
things
that
we
have
done
is
we
have
created
a
status
board,
so
you
can
go
here
now.
So
if
you
so
I
should
skip
ahead.
One
and
and
talk
about
why
this
is
important.
So
the
accept
the
Express
project
is
broken
up
into
three
main
github
organizations.
A
A
So
I'll
talk
about
the
three
sort
of
in
a
top-down
order,
so
the
the
main
one
you're
all
probably
familiar
with
Express
Jas
right,
that's
where
Express
lives,
so
the
the
modules
that
are
housed
under
the
Express
Jas
github
org
are
the
top
level
things
the
middle
where's,
the
you
know,
the
the
the
things
that
are
really
the
Express
layer
below
that
is
pillar
J
s,
so
pillar
j
s
I.
Think
the
tagline
on
the
organization
is
like
BYO
at
a
byof
for
something
bring
your
own
framework.
A
The
idea
is
that
that
is
the
underpinnings
that
you
would
need
to
write
an
Express
of
your
own
right.
So
Khoa.
If
you're,
are
you
all
familiar
with
KOA
yeah?
Okay?
So
when
that
was
that
split
was
being
made,
koa
did
build
directly
on
top
of
a
bunch
of
oh
this
little
videos
is
a
little
bit
slower
than
I
and
I
was
talking.
So
we're
not
to
the
pill,
urges
yet,
but
so
so
koa
built
on
top
of
that
right.
A
A
So
all
that
work
is
spread
across
all
of
these
different
organizations,
all
these
different
repos.
How
would
you
know
where
to
start
the
status
board?
Okay?
So
if
you
go
here
and
go
to
the
project's
tab,
you'll
see
all
of
the
projects
with
their
github
organ
and
their
name.
It
also.
It
shows
a
bunch
of
extra
information
about
the
health
of
the
project.
Things
open,
PR
is
open
issues
if
you're
interested
in
seeing
what
areas
the
express
project
covers.
This
is
your
jumping
off
point.
A
A
So
we
have
top
priorities.
You'll
see
HTTP
two
in
there
you'll
see
typescript
typing
support,
you'll,
see
Xpress,
5,
obviously
right,
I
think
there's
a
bunch,
others
that
need
to
go
in
that
list.
I
think
we
want
more
community
feedback
on
where
Xpress,
5
and
6.
What
features
you
all
really
care
about
and-
and
those
would
be,
the
things
will
will
tag-
is
top
priority.
Those
ones
might
be
a
little
bit
difficult
if
you're
not
super
familiar
with
the
project
right.
A
So
we
also
have
Help
Wanted
good
first
issue
and
discussion
tags,
so
those
are
a
lot
better
places
for
you
to
go.
If
you're,
if
you're
just
trying
to
do
what
I
did
in
2014,
which
is
browse
I'm,
not
sure
if
I
can
contribute
here
yet
I,
don't
even
know
why
I
would
like
what
are
the
modules
that
that
that
I
might
use
in
my
day
to
day
work
that
I
that
I
should
care
about.
A
You
know
how
do
I
even
discover
those.
So
if
you
go
into
the
there's
also
a
section
see
I
should
have
had
this.
That's
the
video
problem
anyway,
I
you'll
see
it
if
we
wait
long
enough
on
this
video,
so
so
that's
a
great
place
to
get
started,
but
then
we
were
talking
with
the
package
maitenance
working
group
and
we're
like
well,
okay,
that
you
know
this
helps
like
this
at
least
centralizes
a
lot
of
the
information
for
people,
but
look
at
all
those
open
issues.
A
You
know
these
top
ones,
don't
really
show,
but
open
pairs
and
open
issues,
there's
hundreds
and
hundreds
and
hundreds
right
and
people
are
opening
new
ones.
All
the
time
and
to
maintain
errs
are
not
enough
to
to
really
answer
all
of
that
right.
So
we
were
talking
in
the
package
mains
for
working
group
about
what
we
could
do
to
help
with
that.
So
this
is
the
second
program
that
we're
working
on
Jewish,
my
partner
in
crime
here
front
row
has
been
working
on
this
with
us.
Thank
you
very
much.
A
A
So
the
reason
why
we,
this
is
the
one
of
the
best
places
to
start
is
because
this
is
what
Doug
and
I
spend
like
most
of
our
time
on
is
answering
people's
questions
right
and
when
we
do
that,
we're
not
pushing
code,
we're
not
pushing
new
releases
right,
we're
we're
doing
the
the
squishy
work
right,
which
is
amazing,
work
and
an
invaluable
to
the
project.
But
it
means
that
the
Technical
Committee
members
sometimes
aren't
doing
as
much
coding
as
we
would
like
to
push
the
feature
set
forward.
A
So
if
you
want
to
come,
it
will
be
f
me
behind
the
microsoft
booth
in
the
sponsors
area,
we're
gonna,
like
I'm
gonna,
be
like
merge
and
pr's
and
like
adding
you
to
two
organizations
like
on
the
spot,
so
come
and
join
us
for
that.
That
will
be
really
exciting.
You
know,
hopefully
we
can
get
at
least
a
couple
of
active
trousers.
A
If
you
all
came
and
signed
up,
it
would
just
change
the
trajectory
of
the
entire
community
of
the
project,
so
I
might
not
be
able
to
merge
all
your
pull
requests
like
like
over
there,
but
but
I
promise.
We
will
get
to
them
also
just
to
mention
here
and
we'll
get
links
to
all
of
this.
This
ref
PR
4055
there's
some.
We
added
some
guidelines
and
some
instructions
on
how
to
get
started
so
we'll
go
over
those
a
little
bit
in
the
you
know
over
in
the
other
area.
A
So
you're,
not,
you
won't
be
alone,
and
it
won't
be
just
like
dumping
you
in
and
saying
good
luck
like.
We
did
to
dress
originally,
but
you
know
we'll
we'll
have
this
and
then
the
goal
would
be
that
we
can
take
some
of
this.
That
we've
worked
on
and
Express
and
and
up
level
it
to
the
package,
maintance
working
group
and
provide
some
structure
for
other
projects
in
the
ecosystem.
A
That
might
benefit
from
our
experience
running
such
a
large,
a
large
ecosystem
of
modules
and
the
time
where
I
sell
out
just
a
little
bit
so
Express
is
not
funded.
Doug
and
I
volunteer
our
times.
I
I
don't
want
to
make
money
off.
Express
I
have
a
wonderful
job
at
Netflix,
but
I
want
money
for
the
project,
so
we
can
do
awesome
things
redesign
the
logo
right.
Can't
you
like,
like
fast.
A
If
I
has
an
awesome
logo
and
then
it's
like
more
Express
is
like
so
old
feeling
right,
something
like
that
where
we
can't
do
it
without
some
some
finances.
You
know
things
like
stickers,
I'm,
gonna,
I
have
a
bunch
of
Netflix
occurs:
where's
the
Express
sticker
Wow
right.
So,
oh
well,
that
was
not
a
good
idea.
Whatever
I
just
touched
it
well
good
thing.
We
were
toward
the
end
of
the
talk
and
this
last
slide
was
like.
Thank
you.
So
that
being
said,
please
we
would
love
to
have
you
on
the
project.
A
The
next
decade
for
express
is
really
about
you
all
coming
and
joining
the
project
right
you,
you
can
be
users,
you
can
be
triage
errs.
You
can
be
technical
committee
members.
It
only
takes
a
little
bit
of
work
like
four
years
right,
but
you
can
get
there.
I
have
faith,
we're
working
on
all
of
the
things
to
make
it
easy
for
you
and
to
make
the
project
great
in
2020.
So
thank
you
for
your
time.
Come
join
me
and
dress
right
after
behind
the
Microsoft
booth.