►
From YouTube: From contributor to maintainer with Nuxt.js
Description
Is it possible to go from core contributor to maintainer? Daniel Roe has done it! Join us on May 5 to learn about his journey in becoming a maintainer of Nuxt.js at 1 pm ET.
A
A
A
A
A
Music
for
me
to
like
be
tweeting
or
posting
I'm
like
we're,
live
right
now,
but
welcome
to
open
source
Friday
y'all.
Basically,
this
is
a
stream
that
I
do
weekly
every
Friday
chatting
with
maintainers
or
core
contributors
about
open
source
projects
that
they're
involved
in,
so
that
we
can
get
more
exposure
to
those
projects
so
that
they
can
also
be
able
to
share
their
experience
of
how
they
were
able
to
start
contributing,
and
so
that
we
can
get
a
chance
to
do
that
as
well.
A
I
just
want
to
say
hi
to
a
couple
of
people
in
the
chat
like
I'll
just
highlight
everyone's
just
saying:
hi
I,
guess
anything
else
where
were
y'all
long,
calling
in
from
or
watching
in
from
someone
asked
nuck.
Oh
someone
said
May
the
fifth
be
with
you,
that's
true,
it's
it's
May
5th
and
someone
said
knockster
next
I
think
we'll
answer
that
question
soon,
but
just
to
be
be
very
clear.
Next
is:
is
the
framework
in
hi
Jen
I
just
wanted
to
say
hi
to
her
as
well?
B
B
B
Next
is
a
framework
building
web
apps
and
it's
based
on
view
and
I
can
get
into
that
in
a
little
bit
a
little
bit
more
before
I
I
started
doing
doing
that.
I
I
was
I,
had
a
small
software
as
a
sort
of
a
startup
before
that
I
was
I,
had
a
creative
agency
world
and
before
that,
I
did
something
entirely
different.
So
this
whole
whole
Tech
world
is
quite
new
to
me.
B
So,
let's
see
so
probably
so
before,
let's
see
when
did
I
start,
so
my
creative
agency
was
a
writing
agency,
so
it
was
about
communicating
clearly-
and
that
was
what
we
did,
but
I
I
have
a
sort
of
tech
bent,
and
so
we
started
doing
stuff.
That
was,
we
would
we'd
refine
a
message
for
a
client
and
then
we'd
do
design,
and
then
we
do
website
building,
and
that
was
the
sort
of
tech
Avenue
and
basically
it
was
a
startup.
So
we
I
would
do
everything.
B
I
would
be
designing
logos
and
sort
of
inkscape
and
and
and
giving
mock-ups
and
then
I'd
build
it
and
so
in
in
WordPress
you
know,
and
and
gradually
from
there
we
pivoted
our
agency.
We
grew
our
team,
we
and
then
we,
then
you
know
obviously
pivoted
into
SAS
as
well,
but
before
that
I
was
actually
a
a
vicar,
a
church
Minister
down
not
not
too
far
away
and
before
that
I
studied
law,
so
I've
I've
done
lots
of
different
things.
You.
B
A
A
B
There
was
viewforge,
which
was
it
was
so
much
fun.
I
would
basically
I
would
always
go
to
that.
So
it
was
a
it
was.
It
was
a
a
conference,
so
everybody
would
come
together,
build
an
app
each
independently.
So
it's
a
bit
of
a
challenge,
you're
sort
of
building
something,
but
in
parallel
with
a
lot
of
other
people,
and
then
there
are
talks
focusing
on
different
particular
challenges
and
in
sequence.
B
So,
let's
first,
this
one
was
building
an
ai-powered
social
media
generator
with
a
chatbot,
and
so
my
bit
of
the
thing
was:
how
do
we
build
the
chat,
the
AI
that
chat
we've
got,
how
does
it?
How
do
we
work
with
the
API
calls
that
we'll
need
to
make?
How
do
we
handle
like
a
session
storing
the
sort
of
past
responses
for
the
user,
and
lots
of
different
people
were
talking
about
different
bits
of
this
thing,
and
so
over
two
days,
people
built
this.
This
app
sounds
fun
to
me.
B
B
B
A
Right,
okay,
so
I
I
feel
like
I
did.
I
did.
I
went
off
track
a
lot
just
because
you
seemed
so
interesting,
but
you
mentioned
you
mentioned
nuts
right.
What
is
your
project
and
then
I
think
a
second
question
I
had
like
following
that
is
like,
and
someone
even
asked
in
the
in
the
comments
next
or
nox
and
I-
think
some
people
get
confused
at
the
two.
So.
B
B
B
It's
philosophic
that
I
could
get
into
Tech
stack
as
well.
We
could
talk
about
the
Veet,
we're
powered
by
Nitro
on
the
server
side,
which
we
built
actually
as
part
of
doing
it,
but
we
spun
out
into
the
framework
that
anybody
can
use,
but
philosophically
it's
about
great
DX,
which
we
think
makes
for
good
user
experience
at
the
end
of
the
day,
minimal,
config,
so
zero
config,
you
can
get
going
really
simply
hopefully,
but
it's
fully
configurable.
B
So
as
you
need
to
change,
the
framework
can
grow
with
you
and
it's
it's.
It's
also
very
Community
Driven.
So
a
lot
of
what
makes
snack
special
is
it
has
a
huge
ecosystem
of
modules
and
other
libraries
built
around
it.
So
you
hundreds!
So
if
you
have
an
integration,
you
can
probably
find
that
someone
has
built
something
for
your
CMS
or
database
or
whatever,
and
you
just
plug
it
in
and
don't
really
have
to
configure
that
or
do
the
hard
work.
So
it
can
abstract
a
lot
of
that
stuff
away.
B
Initially,
they
did
similar
things
so
manage
your
webpack
config
for
you
handle
routing,
so
you
have
a
sort
of
Pages
directory
and
that
gets
turned
into
the
roots
of
your
app
so
handle
things
like
code
splitting
and
other
stuff
that
you
want
want
to
be
configured.
But
without
you
having
to
to
reinvent
the
wheel
every
time
you
start
a
new
project,
but
over
time
they've
diverged
I,
don't
know
how
active
the
sort
of
cross-pollination
is
I
think.
B
Sometimes
we
get
to
say
that
similar
points
without
actually
having
taken
inspiration
from
each
other,
sometimes
I'm
sure
we
do,
which
is
great
right.
We
make
each
other
better
and
and
we're
also
striving
I
think
for
similar
kinds
of
things.
You
want
great
user
experience.
You
want
great
developer
experience
you
want
to
you
know,
hook
into
some
of
what
tech
enables
these
days.
B
A
Think
I
feel
like
that
was
clear,
like
you
essentially
said
that,
like
nox,
it
was
started
off
similar
as
it's
yeah.
It's
like
that's
JS
was
for
react
not
supposed
to
review,
and
it
started
off
as
very
similar
with
handling
routes
and
stuff
like
that.
But
then
it
started
to
diverge
as
like,
as
as
the
community
grew
when
you
all
had
plugins
and
you
all
focused
on
like
creating
a
good
developer.
B
B
A
True,
as
soon
as
he's
Brandon,
the
creator
of
analog
like
in
February,
so
it's
a
good
point
one
question
from
the
audience:
although
I
I
don't
know
if
this
I
don't
know,
if
I'm
highlighting
it
because
I
don't
understand
anything
but
I
I,
don't
think
this
is
related
to
you,
because
next
would
I
don't
know.
You
tell
me
if
this
makes
sense
to
you
any
thoughts
about
The
Versatile
integration
that
was
announced
today.
B
Don't
know
well
so,
basically,
as
part
of
next,
we
aim
to
support
most
providers
with
zero,
zero
config
if
we
can
and
and
you
shouldn't
really
need
to
do
much
to
integrate
or
deploy
to
a
platform.
So
we
have
zero
config
deployed
to
versal,
which
is
nice
not
to
have
to
configure
something
and
we
support
ISR.
B
So
you
can
configure
different
routes
of
your
app
to
revalidate
at
different
times
or
just
to
be
statically
held
in
the
cache
they're
generated
on
first
request
and
after
that
they
persist,
and
so
we
have
it's
currently
configurable
with
the
SWR
flag
in
your
your
config.
So
you
you
do
that
granularly,
so
you
can
either
configure
it
for
your
whole
app,
but
you
can
also
configure
it
just
for
specific
routes
in
your
in
your
app,
and
that
is
that's-
that's
really
powerful.
So
you
can
say
things
like
this.
B
Section
of
the
site
should
be
like
the
blog
section
should
be
ISR,
and
but
this
other
section
here
actually
every
request
we
want.
We
want
to
be
server
rendered,
and
this
section
over
here
should
be
pre-rendered.
You
know
at
build
time,
and
so
all
of
that
is
enabled
by
Nitro
which
I
I
mentioned
before.
B
But
what
was
announced
today
was
vessel's
sort
of
commitment
to
next
and
they're.
A
great
partner
I
had
to
work
with,
and
also
we've
just
released,
support
for
the
new
versal
key
Value
Store,
so
that
is
sort
of
powered
under
the
hood
by
something
called
unstorage
and
if
you
want
to
explore
it
and
if
you're
using
next,
you
just
have
to
upgrade
your
like
refresh
your
lock
file,
upgrade
your
version
of
unstorage
and
you'll,
pull
in
Native
support
for
cells,
KP,
which
is
just
pretty
cool.
A
Wow,
okay
I
am
behind
I
did
not
realize
that
that
was
what
was
in
the
announcement.
Thank
you.
Thank
you.
So
much
all
right.
My
next
question
to
you
is
like
what
is
even
inspired
you
to
get
involved
and
not
next.
In
the
first
place,
because
I
know
you
started
off
as
a
core
contributor.
Why,
like
I
know
Henry,
you
said
you
had
an
agency
and
that's
kind
of
what
brought
you
into
Tech,
but
yeah.
B
So
basically
it
was
we
used
next,
so
I
remember
my
journey
into
view
and
next
and
I
remember.
Basically
we
were
we
were
working
with
with
WordPress,
but
we
wanted
to
make
it.
We
wanted
to
make
it
better.
More
laravel
like
like
to
track
our
dependencies,
for
example,
not
just
upgrade
plugins
by
clicking
a
button
in
the
UI
and
stuff
breaks,
and
you
can't
figure
out
why
but
actually
diversion
them.
So
we
started
bringing
lots
of
stuff
from
laravel
into
our
WordPress.
B
B
The
idea
that
you
don't
just
have
to
have
a
template,
a
PHP
template
and
you
sort
of
put
static
HTML,
but
you
can
actually
have
this
concept
of
binding.
What's
on
the
screen
to
the
data,
your
data
model
and
actually
just
reactively
updates,
which
is
amazing,
the
sort
of
move
from
imperative
to
declarative,
rendering
and
I
remember
going
and
telling
one
of
my
team
at
this
point
it
was.
He
was
just
about
to
start
a
new
project.
B
He
you
know
he
had
to
throw
his
Express,
but
but
I
loved
it
afterwards,
and
so
we
we
sort
of
started
using
next,
both
in
the
agency
world
and
then,
when
I
launched
the
SAS
product
we
built
it
in
next,
and
so
my
involvement
was
really
I.
Guess
I
love
open
source
because
people
give
you
things
for
free.
You
know
people
work
on
things
and
they
share
them
with
you
and
they
say
hey.
This
is
my
gift
and
I
really
felt
I
should
give
back.
B
You
know
if
I
can,
if
I
can
help
make
this
better.
If
I
can
contribute
back
myself,
why
wouldn't
I?
You
know
it's?
It's
a!
It
felt
really
rewarding
to
be
part
of
this,
this
ecosystem
and
it
it
felt
it
really
does
feel
very
relational
to
me
like
open
source.
This
is
something
someone's
giving
I'm
giving
that's
what
this
is.
That's,
what's
going
on
here
and
I,
really
really
I
know
a
lot
of
people.
Think
of
transaction.
They
want.
They
feel
more
like
that.
B
I,
don't
at
all
I
feel
like
every
contribution
in
open
source.
For
me,
it's
relational.
It
is
about
people
it's
about
giving
and
that's
that's
really
what
I
felt
at
the
time,
and
so
that's
how
I
got
started
really
so
I
just
started
contributing
other
projects.
We
were
using
first,
a
module.
Actually,
it
happens,
deploy
into
the
cell.
We
had
a.
B
We
had
a
our
own
Arc
of
deployment
back
in
the
early
days
when
it
was
zeit
now
and
there
was
a
you-
could
deploy
a
Docker
image
and
anyway,
so
I
started
getting
involved
on
that
side
of
things
for
next
and
gradually
started
doing
more
things,
building
a
little
module
here
or
there
and
at
some
point
I,
do
remember
this
sort
of
Sebastian
astronauts.
Just
messaging
me
and
saying
hey.
B
Would
you
like
to
be
a
an
ax
maintainer
and
I
was
so
honored?
It
was
honestly,
it
was
totally
out
of
the
boo,
so
I
was
not
expecting
that
at
all,
but
I
was
absolutely
delighted
and
and
actually
wasn't,
that
much
longer
I
think
it's
just
about
a
couple
of
months
when
he
actually
asked
me
to
be
part
of
the
core
team,
which
again
it
was
just
a
sort
of
whoa.
This
is
incredible
because
I
mean
partly
because
this
wasn't
my
background.
B
Also,
you
know
it's
not
like
I'm
flush
with
you
know:
Fang
companies
and
I've
been
in
Tech
since
whatever
and
I
you
know,
I
I
I,
don't
I,
don't
think
I
could
Point
people
to
some
kind
of
proof
that
I'm
any
good.
You
know
so
to
be
actually
to
further
the
author
of
a
framework
to
say:
we'd
love
you
to
be
on
the
core
team.
B
It's
it's
really
it's
really
validating
and
it
doesn't
actually
help
this
hugely
with
the
the
Imposter
syndrome,
but
it
was
really
nice
and
so
so
yeah
I
started.
I
was
part
of
the
poor
team
and
relatively
for
a
completely
unrelated
reason.
I
was
I
shot
down
my
my
startup
and
and
basically
Sebastian
Michonne,
said:
hey
I
hear
that
you
might
have
some
more
time.
B
A
B
A
B
Was
I
scared?
I
was
not
scared,
I,
don't
think,
although
I
think
that
I
do
very
much
and
I
don't
know
whether
this
is
I
also
live
very
much
in
the
moment,
so
I'm
not
maybe
very
good
at
accurately
recalling
what
I
was
thinking
in
the
past,
but
I
do
very
much
feel
that
the
tools
of
review
and
PR
are
very
relational
like
when
someone
clicks
request
changes
on
a
PR
I
like
I
I'm
like
oh
goodness,
me
I
have
been
rejected,
like
I
mean
and
I
I
try
and
realize.
B
No,
it's
not
that
and
actually
I
have
started
using
it
myself,
not
in
any
way
just
to
keep
track
of
like
what's
going
on
in
the
list
of
of
PRS
rather
than
but
it
it
can
feel
so
personal.
It's
like
my
sorry,
my
PR
wasn't
good
enough
and
and
that,
like
the
whole
dialogue
of
back
and
forth,
particularly
when
you're
when
you're
creating
a
PR.
Actually
this
happened
only
the
other
day,
I
I
opened
a
p.
I
this
is
a
completely
new
framework.
I
was
I,
was
writing
a
talk?
B
It
was
going
through
the
docs
just
figuring
out
how
to
go.
There
was
an
error
in
the
dark,
so
I
opened
a
PR
to
fix
that
mistake
and
basically
had
a
long
conversation
with
someone
who
said
no,
it's
right
and,
in
the
end,
I
convinced
them
that
no,
it
was
in
fact
wrong.
So
they
opened
another
PR
which
is
identical
to
mine
and
there's
got
merge
and
I
have
got
to
say
like
that.
That
I
have
felt
it
didn't,
feel
great.
Did
it
and
like
that
the
whole
I
thought
anyway.
B
I
think
that
I
think
that
when
you're,
creating
that
that
first
contribution,
whether
that's
a
PR
or
whether
it's
issue
triage
or
comment
or
helping
out
on
a
Discord
server
or
something
I,
don't
know,
there's
a
lot
at
stake.
It
feels
like
there's
a
lot
at
stake
and
you
can
really
take
it
to
yourself
and
feel
feel
quite
it
can
have
quite
a
personal
feel
about
it.
B
So
I,
don't
know
if
that
product
doesn't
answer
your
question
at
all,
but
I,
don't
remember,
feeling
scared
or
anxious,
but
I'm
sure
how
I
was
treated,
had
a
huge
impact
on
what
on
the
fact
that
I
was
able
to
continue
contributing,
because
you
know
we're
people
we
like
to
feel
valued.
We
want
to
be
seen
and
recognized
for
Who,
We,
Are
and
I.
Think
you
know,
I
felt
I
was
so
yeah.
A
No,
that
was
an
amazing
answer.
I
I,
like
I,
think
it
was
interesting.
You
know
a
lot
of
people
say
at
first.
They
were.
They
were
scared
to
contribute
to
open
source
I
love
how
you
were
just
like
I'm,
just
gonna
go
in
with
no
inhibitions,
but
then
you
still
recognize
that,
like
it
can
be
scary
because
we're
putting
our
ourselves
out
there
and
in
the
open
to
essentially
for
our
work,
our
our
intellectual
property
or
whatever.
A
A
B
A
B
B
So
if
you're
encountering
the
framework,
it's
because
you're
probably
reading
the
documentation
and
if
something
isn't
clear
to
you,
that
is
the
very
very
first
thing
that
you
could
possibly
fix
about
it
because
you've
got
you,
don't
you
you
haven't
even
got
to
the
point
of
using
it.
I
don't
know.
I
I
I
certainly
think
a
lot
of
people
seem
to
start
contributing
with
with
the
docs
but
yeah.
It's
definitely
definitely
not.
The
entry
level
sort
of
in
terms
of
value
hits.
A
I'm
not
I
mean
sometimes
it's.
It's
really
needed.
Translating
docs
fixing
errors
like
those
are
underrated,
undervalued
things
not
like
you
said
it's
not
entry
level.
It's
still
helpful
and
I
guess
Jen
was
asking
me
so
I'll,
okay,
mentally
prepare
yourself
for
after
the
the
few
comments.
I
read
that
we're
going
to
jump
into
the
demo,
but
I
guess
Jen
was
asking
me
what
was
my
first
open
source
PR?
A
Actually
it
was
open
sourced.
Just
like
you
before
I,
oh
I,
think
you
wrote
it
right
here.
Yeah
before
I
joined
GitHub,
like
I,
did
an
interview,
and
my
presentation
was
all
about
like
how
I've
never
contributed
to
open
source
before
and
I
didn't
feel
like
and
I
felt.
I
was
giving
suggestions
of
like
how
GitHub
can
make
it
more
approachable
and
then
basically,
they
hired
me
and
BW
was
like.
A
If
you're
going
to
work
here,
you
should
probably
contribute
to
open
source
and
made
me
contribute
to
his
project
and
similar
to
what
Daniel
said
like
At.
First
I
was
scared,
but
because
the
community
was
so
welcoming
and
and
like
really
kind
I
was
like.
Oh,
this
isn't
scary
at
all
like
they're,
really
nice
here
and
then
David
from
archetype
said.
A
One
of
the
first
big
open
source,
PRS
I
worked
on
was
a
massive
feature
to
do
relational,
schema
and
inference
the
maintainers
kept
asking
me
to
do
more
and
more
on
it
with
the
promise
of
merging.
Oh,
that's
like
actually
really
discouraged,
but
after
months
they
ended
up.
Scrapping
the
repo,
however
I
mean
sorry
honestly
felt
burnt
out
for
months
after
the
maintainers
make
a
big
difference
in
terms
of
how
that
experience.
A
B
Up,
okay,
yeah
I
totally
agree
with
that.
Okay,
so
here
we
are.
This
is
a
a
minimal
next
project,
I've
not
done
anything
other
than
install
the
dependencies,
and
basically
you
you
start
a
new
project
by
running
Nazi
in
it,
my
app
or
something
like
that,
and
that
gives
you
this
and
then
I
I've
just
installed
the
depths.
The
first
thing
you
might
do
is
start
with
Dev
server.
B
You'll
get
a
message
telling
you
to
do
that
when
you
start
up,
this
is
The
Edge
Channel,
because
I've
got
a
script
ready
to
to
start
start
an
edge
Channel
version
of
next
but
you'll
see
numbers
that
are
a
bit
shorter.
When
you,
when
you
run
that
that
command
and
basically
out
of
the
box,
you
get
a
you,
get
a
just
a
sort
of
Welcome
to
Knox
page
about
Supercat,
and
that
is
rendering
this
app.view
file.
B
B
B
So
you
might,
you
might
do
something
that
that
has
to
be
set
up.
When
you
start
your
your
application
and
sometimes
you
might
want
to
return
something
or
make
it
globally
available
to
the
rest
of
your
app,
and
so
you
might
do
something
like
this,
you
might
have
some
kind
of
or
off
that
you
set
up
that
wants
to
be
used
everywhere
and
you
could
you
could
do
that
like
login
you're
gonna
have
something
more
going
on
than
that.
B
But
anyway
you
you
can
have
a
next
plugin
that
you
you
set
up
now.
One
of
the
things
you'll
notice
is
that
we
have
a
TS
config
there
by
default
and
it's
actually
extending
a
generated
TS
config
and
you
don't
really
need
to
know
typescript
or
worry
about
what's
going
on
behind
the
scenes,
but
we
like
to
make
all
of
what
we
enable
all
the
features
that
next
offers
discoverable
and
usable
through
your
IDE
and
the
way
we
do.
That
is
we
use
typescript
and
we
also
get
the
benefit
of
type
checking.
B
So
you
don't
need
to
worry
about
that,
but
you
see
actually
I
have
type
type
safe
access
to
this
thing
that
I've,
just
just
added
into
my
app
has
has
other
stuff
as
as
well
so
things
like
middleware
I
might
want
to
to
have
well
I'll
call
it
auth
as
well.
I
don't
want
to
have
some
kind
of
middleware.
That's
going
to
check
that
I'm
authenticated.
B
B
Take
us
back
to
the
home
page,
something
like
that
and
then
what
I
could
say
here.
I
could
actually
use
it.
So
I
could
say
this
page
is
going
to
have
some
middleware
that
applies
to
it
and
that
middleware
actually
oops
I,
don't
know
if
you've
got
that,
it's
actually
a
piped
for
me.
So
it
knows
that
that
middleware
could
be
off
or
or
nothing
else,
and
if
I
get
it
wrong.
B
A
Think,
oh,
you
are
not
I
think
this
is
really
interesting.
I
know
we
have
typescript
people
here
in
the
in
the
that
are
watching
so
I'm
sure
that
they're
loving
it
someone
said
string,
intro,
I
can't
even
say:
interpolation
is
fun.
Sorry
I
cannot
read
and
then
David
said
just
waiting
on
typescript
to
enable
access
to
FS
from
within
the
type
system,
so
that
no
generated
code
is
required.
B
Maybe
you
create
a
blog
and
you
want
to
have
and
a
sort
of
a
dynamic
page
which
is
going
to
depend
on
the
like
the
blog
ID,
and
so
you
can
actually
get
access
to
it
like
this,
you
can.
You
can
use
these
square
brackets
and
you
could
you
could
even
do
something
like,
but
a
dynamic
pattern
like
that
and
and
it's
going
to
make
it's
only
going
to
match
it
if
you
hit
blog
entry-21
or
whatever
so
Dynamic
stuff
works
even
a
bit
more
complicated
one.
B
So
if
you,
if
you
want
parameters
to
be
optional,
you
can
use
sort
of
double
brackets
like
that
and
you
can
have
nested
routes.
So
maybe
you
have
like
a
page
which
wraps
some
child's
Roots
and-
and
you
can
do
that
as
well,
using
using
the
file
system,
this
isn't
meant
to
be
a
limiting
factor,
though
this
is
meant
to
make
it
simpler
and
easier
to
understand
where
the
page,
that's
rendering,
what
you're,
what
you're
looking
at
comes
from.
B
You
can
actually
fully
customize
it
using
that
defined
page
meta
macro
that
I
showed
earlier,
so
you
could
actually
put
a
custom
path
which
would
use
any
kind
of
redbacks.
But
actually
you
could
say
you
know,
IB
can
only
be
numbers
or
something
like
that.
You
could
also
add
aliases,
and
so
this
this
should
also
be
served
by
blog,
hello
or
whatever,
and
so,
like
you
have
full
control
to
do
whatever
you
want,
but
by
default
that
file
system-based
routing
is
a
really
nice
way
in.
B
I
didn't
mention
up
to
now
the
fact
that
we
have
a
server
integrated,
so
you
can
create
server
routes
and
we
use
a
framework
that
we
built
called
H3,
which
is
an
event
handler
based
framework.
So
you
can
just
directly
return
Json,
for
example,
and
it
gets
so
so
you
could
do
something
like
this
hit
that
endpoint,
what
is
it?
Api?
B
A
it's
just
going
to
return
Json
for
me
and
it's
going
to
set
the
content
type
and
whatever
else
you
might
need-
and
you
can
then
use
that
throughout
the
rest
of
your
app
in
an
we
call
it
an
isomorphic
way,
which
sounds
very
confusing.
But
what
it
means
is
on
the
client,
oh
yeah,
and
we
get
pipe
safe
access
to
the
endpoint
and
also
end-to-end
type
safety
in
terms
of
the
data.
That's
coming
back
from
it.
B
What
that
isomorphic
thing
means
is
that
on
the
server
this
isn't
a
network
request,
it's
just
a
function.
Call
you
directly
hit
the
function,
which
means
you
don't
have
to
hit
the
network
layer
it's
really
fast
and
on
the
client
it
becomes
a
network
request,
and
so
you
don't
need
to
worry
about
how
it's
happening.
It
just
just
works.
B
A
B
Really,
it's
really
lightweight
so
going
from
next
two
to
three:
we
had
something
like
a
30
40
decrease
in
bundle
size,
which
is
nice
right.
That's
the
direction
we
want
to
be
going
in,
but
the
but
yes
so
lots
of
stuff
that
that
I
could
talk
about.
I
could
tell
you
about.
We
have
layouts,
for
example,
you
can
create
layouts
that
are
shared
across
your
app.
You
I
could
talk
about
some
of
views.
Interesting
features.
B
You
can,
for
example,
take
all
of
the
data
that
you
use
on
any
route.
We
can
extract
it
at
a
build
time
if
we're
pre-rendering
your
pages
and
then
you
never
need
to
actually
hit
those
routes
at
runtime
it's
put
into
a
payload
which
can
actually
then
just
be
downloaded
as
a
sort
of
static,
Json
sort
of
file,
which
is
quite
quite
useful
as
well,
and
we
just
released
an
experimental
feature
where
you
can
even
include
like
complex
JavaScript
objects.
B
So
I
did
a
stream
recently,
where
we
put
we
encoded
promises,
so
you
could
return
a
promise
on
the
server
and
get
the
value
on
the
client.
So
so
you
it's
like
streaming,
so
you
basically
you
render
the
page
and
then,
when
the
the
server
promise
resolves,
then
your
client
data
updates,
and
that
was
very,
very,
very,
very
cool
because
it
meant
you
get
that
initial
response
immediately.
But
the
the
request
fully
happens
on
the
server.
A
But
I
think
I
think
this
made
people
get
like
excited.
Like
our
type
said:
wow,
that's
amazing,
someone
was
saying
like
typescript.
Is
life
embrace
it
so
I
I'm
excited
like
I,
didn't
realize
that
all
these
features,
like
I,
didn't
realize
how
powerful
Nook
was
so
this
is.
This
is
cool
and
somehow
it's
already,
we
already
been
speaking
for
41
minutes.
It
didn't
feel
that
long.
A
B
Those
are
great
because
generally
we
give
that
if
we
think
there's
enough
information
there
for
you
to
make
a
go
at
it
without
having
the
back
a
lot
of
background
in
the
repository,
it
doesn't
mean
it's
an
easy
thing
to
do
by
the
way.
It's
not
like
this
is
easy
code,
but
it
means
you
should
have
enough
there
to
to
get
going
a
lot
of
the
issues.
Mark
documentation
are
good
to
get
get
going
because
they
often
again
have
the
information
in
the
issue.
B
B
But
if
you
can
then
pick
that
and
actually
make
the
pr
you
will
be
making
so
many
people's
lives
easier,
and
then
there
are
the
things
that
are
explicitly
marked
as
bugs
and
often
they'll
have
a
priority
as
well
and
that
those
can
be
great
to
pick
up.
I
mean
I,
I
love
it
when
I
see
that
happen.
But
the
key
thing
from
my
point
of
view
is
as
a
maintainer
I
love
it.
B
When
people
contribute
please,
you
should
feel
free
to
message
me:
you
can
get
in
touch
on
Twitter,
you
can
get
in
touch
and
get
and
probably
not
GitHub
I
mean
you
can
obviously
open
an
issue
or
PR.
But
you
can
message
me
on
Discord.
If
you
have
questions
you
don't
understand
the
right
approach.
You
have
an
idea.
B
I
really
am
happy
to
do
that
and
if,
if
I
don't
respond,
it's
not
because
I'm
not
happy
in
my
opinion,
because
I'm
busy
or
something
ping
me
I'm,
I'm
I'd
really
be
delighted
and
I.
Don't
think.
That's
just
me,
I
think.
A
lot
of
maintainers
are
just
really
very
happy
to
be
contributed
by
people
who
want
to
to
be
to
be
part
of
the
project
and
and
to
help
out.
A
A
If
you
wanted
to
to
contribute
to
the
repo
and
I
love
that
you
said
that
you're
you're
open
to
helping,
but
you
also
gave
that
disclaimer
like
yo
maintainers,
are
busy.
They
want
to
help,
but
they're
also
busy,
so
give
them
that
time
to
be
able
to
respond
back
to
you.
Don't
don't
get
too
too
demanding,
but
they
will
oh
or
just
reaching
out
to
someone
within
the
community.
I
found
that
that
really
helps
me
when
I'm
in
an
open
source
project
and
I'm
stuck
I
feel
like
that
was
the
difference
of
me.
A
Not
contributing
to
starting
to
contribute
is
like
I
started,
actually
interacting
with
the
other
people
within
the
community,
and
then
I
was
like
okay
now
I
have
Clarity
on
what's
going
on
within
this
repository
and
I,
feel
part
of
the
community
and
I
feel
like
I
can
ask
for
help
if
I
wanted
to
this
is
an
interesting
question.
I
guess
some,
please
tell
us
a
bit
about
I,
don't
know
what
what
you
could
say,
but
please
tell
us
a
bit
about
core
members.
Insiders
contributors,
I
think
can
be
big.
B
B
I
mean
I,
guess
with
any
open
source
project.
It's
not
like
an
external
body,
but
this
is
what
we're
aspiring
to
have
a
look
there.
Basically,
the
core
team
are
a
smaller
team.
I
think
we're
about
six
at
the
moment
and
there's:
there's
contributors
are
it's
basically,
anyone
who
contributes,
and
so
you
don't
need
a
stamp
or
anything
to
be
to
be
counted
as
a
contributor.
B
If
you
are
contributing,
you
are
a
contributor
there's
this
insiders
group
which,
if
you,
if
how
would
I
how
would
I
describe
that
it's
it's
just
a
group
of
people
who
are
involved
in
making
stuff
with
next,
so
they
are
key
contributors
to
the
framework
ambassadors
or
content
creators,
Library
authors
or
module
authors.
If
that
is
you,
let
me
know,
because
you'd
be
very
welcome
to
be
part
of
that
group.
B
B
A
B
It's
it's
people
who
believe
in
it.
It's
people
who
are
committed
to
it
and
people
who
make
it
better,
but
obviously
there's
a
million
caveats,
and
just
because
you
are
all
of
those
things
and
a
project
doesn't
mean
you'll,
become
part
of
the
core
team,
because
you
know
it's
about
the
gaps
as
well.
What
does
the
core
team
not
have?
What
who
do
they
need
to
bring
in
you
know,
so
a
million
million
asterisks
there,
but.
A
Yeah
I
think,
that's
all
fear
yeah!
Do
it
because
you,
you
you're,
passionate,
not
because
you're
like
I'm
doing
this,
so
I
can
become
a
maintainer
like
that's.
Maybe
the
wrong
mindset
and
we'll
leave
lead
you
in
the
wrong
path.
My
my
last
question
before
I
move
into
some
of
the
fun
questions
and
I
know.
I
didn't
really
follow
any
of
the
the
agenda
that
I
wrote.
Sorry,
but.
A
B
The
the
things
that
I
have
to
watch
out
for
in
myself
are
Kingdom
building
so
wanting
to,
because
there
are
lots
of
projects
doing
similar
things
pick
any
area
that
any
project
any
open
source
Library.
There
are
other
things
out
there
doing
something
similar
and
then
people
will
start
saying
things
like.
Oh
I
prefer
this
other
solution,
and
it
is
so
hard,
but
it
is
so
important
to
basically
quash
that
voice
in
you.
Basically,
that's
great
if
another
project
does
well,
that
is
really
good.
B
That
is,
but
that
is
a
challenge
like
that's
hard
all
the
time,
because
you
want
your
own
thing
to
be
great
right,
you
want
it
to
be
good,
but
it's
not
a
pie
like
we're,
not
all
fighting
for
slices
of
pie
or
we're
fighting
to
make
the
pie
get
bigger.
That's
what
we
want.
We
want
everything
we
want
all
of
us
to
get
better,
and
so
that
is
something
I
think
that
is,
that
is
a
challenge.
B
I
think
it's
also
a
challenge
to
be
too
easily
to
put
too
much
of
yourself,
your
own
ego
into
something
I
find
so
if
I
say
something
or
I
do
something
and
I'm
wrong.
It's
really
easy
to
double
down
and
be
like.
How
dare
you
question
it?
No,
this
is
how
it
will
be,
but
all
the
time
I
find
I
am
wrong.
B
B
Actually,
isn't
that
a
little
bit
more
about
me
and
how
I've
read
them
and
actually
a
little
bit
about,
maybe
where
I
was
that
day,
so
I
think
weirdly
the
challenges
I've
found
with
being
a
maintainer
are
less
about
other
people
and
more
about
me,
I,
don't
know
how
whether
that
matches
anyone
else,
but
that
I
I
would
say
that
I
would
also
say
that
in
comparison
to
having
an
agency
or
a
startup
open
source
leadership
is
a
lot.
It's
it's
a
lot.
It's
it's!
It's
a
lot
more
fun
in
some
ways.
B
It's
also
a
lot
harder
in
other
ways,
because
you
don't
have
a
team,
you
pay.
Who
will
do
what
you
tell
them
to
do?
You
know
everyone
involved
in
the
project.
Is
there
because
they
believe
in
it,
but
also
they
are
totally
unconnected
like
that
that
they
might
do
anything,
they
might
say
they'll
do
something
and
not
do
it.
You
know
it's.
B
A
Leadership
is
hard.
David
from
archetypes
are
definitely
the
less
stressed.
I
am
the
easier
it
is
to
deal
with
negativity
and
I
even
relate
with
the
whole
like
when
people
are
like
I
like
this
project,
better
or
whatever,
like
I'll,
write,
a
blog
post
and
be
like
Oh
GitHub
co-pilot.
Does
this
or
give
a
post
faces?
Does
this
and
then
someone's
like
well
and
grow
up?
Does
the
same
thing
and
I'm
like
I'm,
not
talking
about
Edgar
off
here,
but
I,
don't
need
to
I.
A
B
B
It
was
basically
magic,
like
you,
draw
some
stuff
on
a
screen
and
make
the
cue
basic
was
basically
text,
Adventure
type
games
and
it
was
all
sort
of
go-to
go
to
this
and
you
could
clear
the
screen
CLS
clear
the
screen,
but
it
was,
it
was,
you
know,
very,
very
basic
stuff,
so
to
speak,
and
then
Visual
Basic
was
was
you
know
you
started
drawing
buttons
on
the
screen.
You
could
click
them,
and
you
know
you.
B
You
put
people
complain
about
JavaScript
now
but
like
that
you'd
compile
that
app
and
this
was
ages
ago
and
it
would
still
be
5,
12,
20,
meg,
or
something
like
that.
So
they
were
huge
things.
But
again
it
was
magic
because
I
mean
I.
Remember,
I
made
all
kinds
of
little
apps.
There
was
one
I
mean
like
I,
taught
myself
to
go
to
us
about
12
or
13.,
and
Visual
Basic
and
I
made
I
made
one
app.
B
That
would
basically
look
exactly
like
the
Windows
login
screen,
and
so
you
it's
like
I
thought.
I'll
get
my
parents
password
I'll
come
down
and
I'll
type
it
into
the
computer
and
it
was
designed
it
would
basically
sort
of
throw
an
error
and
then
close
itself.
So
you
would
then
have
the
real
Windows
login
screen
nice.
B
They
they
might
not
even
know
it
would
just
look
like
it
failed
and
I
wrote
another
app
that
basically
would
and
you
could
hit
a
hotkey
and
it
would
restore
like
a
window
like
a
screen
and
I
basically
used
to.
Instead
of
doing
homework,
I
used
to
read
Project
Gutenberg
ebooks,
it
was
amazing
and
I
had
so
much
fun.
I
had
a
sorry,
my
childhood
meant
I've
been
very
interesting,
but
I
I
loved
it
I
was
fantastic,
but
I
wasn't
allowed.
B
I
wasn't
allowed
to
read,
I
had
to
do
my
homework,
you
know,
calculus
needs
to
be
done,
so
I
would
but
I
would
basically
I
just
press
the
hotkey
homework
back
on
the
screen.
So
like
I
I
it
was,
it
was
cool.
So
you
could.
You
could
basically
come
up
with
an
idea
and
you
could
do
it
and
there
was
just
very
little
friction
or
barrier
to
entry.
I
later
learned,
I
think
C,
plus
plus
as
like
a
class
in
high
school,
but
that
was
so
much
more.
It's
so
much
more
friction.
B
B
A
This
I
was
very
confused.
The
whole
time
I
think
I
made
like
a
basic
Pizza
app
and
like
that
was
the
only
thing
I
understood
throughout,
like
I
think
I
took
classes,
Visual
Basic
one
and
two
everything
else
after
that
Pizza
app
just
went
over
my
head,
I
was
like
I,
don't
know
what
I'm
saying
but
I
did
I
did,
learn
it
and
I
think
it
was
a
good
starting
point.
B
B
Yeah
I,
think
so,
if
money
wasn't
an
object,
I
would
probably
be
sort
of
in
nice
places
somewhere
hot,
maybe
or
skiing
in
the
winter
and
I
would
I
would
be
I
would
be
coding
in
the
the
evenings.
I'd
be
skiing
in
the
mornings.
That
kind
of
thing
and
in
terms
of
what
I
would
be
doing,
I'll
probably
be
doing
exactly.
This
I'd
probably
be
hacking
away
on
next.
So
you
know
I
I
like
it.
B
It's
I
do
this,
because
it's
fun,
I,
think
and
I
think
a
lot
of
of
maintainers
do
because
honestly
I
think
there
are
a
lot
of
other
Alternatives
that
would
so
I
mean
I'm,
I'm
full-time
I
do
some
consultancy,
but
but
most
of
my
time,
I'm,
maintaining
next
I'm,
supported
by
sponsors
and
I,
could
probably
get
a
much
better
pay
job,
but
I
love
it.
You
know
so
so
there
we
go.
So
it's
it's,
not
a
real
question.
A
A
B
A
A
B
B
It
compiles
to
normal,
regular
Expressions,
but
basically
it's
powered
by
typescript,
and
it
will
protect
you
from
a
lot
of
the
issues
that
you
can
face
without
without
care
because
JavaScript
and
typescript
don't
protect,
you
like
you,
can
run
a
match
all
command
on
a
non-global,
regular
expression.
You
know
there
are
lots
of
things
you
can
do,
and
this
basically
can
solve
that
for
you
and
check
out
one
more
thing
called
Fontaine
it.
B
Basically,
it's
spells
f-o-n-t-a-I-n-e
and
it
it
helps
get
rid
of
layout
shift
that
occurs
when
a
web
font
loads.
So
if
you
have
a
sort
of
fallback
font
like
Ariel
and
the
web
font
loads-
and
your
page
goes
like
that-
you'll
have
a
web
vitals
hit
and
this
basically
is
automatic.
It
injects
a
bit
of
CSS
into
your
project.
It
works
on
next
on
next
on
anything
astroductusaurus
whatever,
and
it
basically
will
get
rid
of
some
of
that.
So
with
no
cost
to
you.
A
Also,
if
you
wanted
to
understand
the
whole
governance
body
and
all
of
that
they
have
knock
slash
governance,
also
elk.zone.
If
people
are
into
Mastodon
like
you
said,
and
you
can
contribute
and
then
we
got
magic,
regex,
I,
don't
I,
don't
remember
everything
but
I
guess
it
makes
projects
better
and
then
also
check
out
Fontaine,
so
I
mean
people
can
rewatch
this
stream
if
they,
if
they
feel
they
missed
something.
A
Thank
you
so
much
for
your
time,
Daniel.
This
was
a
really
enjoyable
conversation
and
I
learned
like
a
fountain
of
information
from
you,
and
also
thank
you
so
much
to
the
audience.
I
always
love
how
engaged
they
are
like
the
comments
they
add
in
and
the
questions
I
feel
like
it
makes
it
more
fun.
So
it's
not
like
we're
just
talking
to
each
other.
It's
like!
Oh
there's,
other
people
here
that
we
could
chat
with.