►
From YouTube: Fetch in Node js
Description
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/165
A
A
A
A
Unless
you're
super
super
I
sight,
you
might
not
fit
this.
So
if
you
want
to
come
closer
whatever
you
might
want
to
so
problems
have
promised
or
fetch,
but
is
a
complex
pack
that
has
a
bunch
of
a
bunch
of
nice
properties
for
the
web.
Okay
and,
first
of
all,
it's
time
integrate
it
into
the
caching
model
of
the
browser.
Okay,
the
fax
pack.
It's
it's
as
a
food
truck
in
fact
dedicated
well.
Caching
works
so
do.
A
A
E
B
A
A
So
those
are,
you
know,
more
high-level
topics,
okay,
just
flag.
In
my
opinion,
if
you
are
different
opinion
of
those
topics,
you
know
please
let
me
know,
but
I'm
I
think
I
keep
going.
Please
me
whatever
you
want,
so
this
is
a
high-level
okay
and
on
top
of
these
I
level
search,
we
have
other
things
which
is
its
global
okay,
and
this
is
problematic
because
all
of
these.
A
A
A
A
A
A
A
E
A
A
A
A
F
A
A
E
H
Rather,
to
an
API
for
working
with
I
think
within
the
ecosystem,
it's
become
a
fairly
idiomatic
way
of
writing
code
when
I
sit
down
and
I
want
to
make.
You
know,
like
some
sort
of
request,
to
get
some
sort
of
resource
over
the
wire
I
reached
for
a
mid
fetch
almost
straightaway.
If
we
want
to
write
code,
that
can
you
know
be
platform-independent,
it's
really
to
me.
I
will
go
and
write
something
like
if
not
fetch
then
require
no
fetch
and
I.
H
Think
that,
especially
as
we
move
towards
the
SM,
we're
like
doing
that
kind
of
dynamic,
poly,
filling
top
level
will
make
it
a
little
easier,
but
it's
still
not
necessarily
something
that
we're
like
jumping
up
and
joy
about
a
pattern
to
be
following,
so
it'd
be
really
great
to
not
have
to
polyfill
it.
In
the
same
way,
it.
H
I
I
Library
out
there
I'd
gone
through
and
actually
implemented,
fish
quotes
around
that
for
nerdcore.
It
didn't
implement
the
security
it
didn't
implement.
The
caching
you
didn't
eat
you
streams.
If
I
could
didn't
hit
my
muscles
on
that
list,
so
I
didn't
throw
it
out
there
because
it
wasn't
actually
fetched
it.
Had
the
name
of
the
company
was
the
the
way
that
works
so
once.
A
So
that
is
more
or
less
then
the
problem
like
I
just
wanted
to
state
the
problem,
and
you
know
because
question
mark
likes
shipping.
This
is
going
to
be
a
journey,
but
it's
not
going
to
be.
It
is
it's
important
that
we
need
we
ship
some,
so
it
seemed.
We
have
two
things.
We
have
two
requirements
and
we
need
a
better
HTTP
client
for
node
ship
within
node
itself
and
we
need
to
support.
We
will
need
some.
C
J
A
B
A
A
A
E
A
Treats
okay
now
at
the
beginning,
there
was
some
thoughts
off
and
some
you
know
very
bad
blood
being
spilled
whatever,
and
about
this.
There
is
I
am
of
the
opinion
that,
because
of
the
sheer
amount
of
number
of
downloads
and
usage
of
notes
traits,
we
will
never
be
able
to
replace,
not
suing.
We
work
with
districts.
Okay-
and
this
is
the
we
need
to
live
with
that
mask.
That
is
not
stressful.
Okay,.
B
A
A
A
F
E
A
A
A
B
E
B
A
E
A
I
C
D
A
Is
not
simple
in
any
form,
so
it
needs
a
lots
of
people
working
there's
a
lot
of
people
complaining
that
fetch
is
not
there
and
not
and
not
enough
people
say:
oh,
how
can
we
have
this?
How
can
we
make
this
work?
How
do
you
address
the
compatibility
with
the
rest
of
the
system
and
work
on
this?
So
why
not,
if
there's
a
bunch
of
people
that
is
willing
to
help
and
work
on
this,
is
we
can
spin
up
a
repository.
B
A
Organization
where
we
can,
you
know,
tinker
with
and
experiment
and
then
do
a
massive
PR
to
know
when
we
already.
This
model
has
been
used
by
http/2
and
models
to
ship
them.
So
it's
a
proven
module
for
you
know
managing
very,
very
big
and
complex
changes.
We
have
a
lot
of
ramifications,
so
we
might
want
to
do
that,
but,
as
I
said,
it
requests
people
so
there
of
their
volunteers.
E
A
Some
of
the
problems
of
fetch
the
way
note
works
and
the
way
we
compose
node.js
applications
in
the
process
in
real
life
is
that
non
je
having
it
is
a
global
with
a
global
connection,
pool
and
so
on.
All
those
things
are
potentially
problematic
for
node
itself.
So
I
have
this
idea
of
meet
fetch
API.
A
B
C
A
A
A
A
F
A
A
B
D
D
I
Answer
is
yes,
we're
ups
are
going
to
need
them
fetch
as
a
higher
level.
Abstraction
does
not
expose
enough
detail
to
higher
to
actually
make
use
for
this
specific
features,
so,
basically
to
the
missionary
like
push
streams,
for
instance.
There's
nothing
there
that
to
do
that,
so
we
actually
need
a
little
client
or
client
side
that
exposes
for
HP
three
we're
actually
have
two
clients.
There's
a
quic.
A
There
are
a
couple
of
reasons:
the
first
one
it's
it's
numb,
probably
close
to
number
one
complaint
from
the
folks
on
the
web
platform
so
and
currently
using
notes
such
as
a
certain
series
of
you
know,
compatibility
issues
around
as
I
said
connection
pooling
by
default.
It
has
no
connection
pooling,
which
means
that
if
you're
writing
a
react,
app
server
side
run
to
react,
application
or
it
me
and
from
the
global
object.
A
F
H
A
A
H
So
I
have
a
branch
and
nothing
works,
but
I
have
like
one
or
two
commits
and
basically
into
the
debts.
Folder
and
I
brought
the
wind
platform
tests
because
I
don't
have
trees
in
here.
Joy
did
something
really
an
awesome
work
with
documenting
and
automating
the
process
of
vendor
in
a
web
platform
tests.
H
So
there's
a
whole
bunch
of
tests
for
fetch,
so
I
got
the
tests
and
then
I
was
trying
to
wire
up
node
fetch
and
he
was
like
super
naive
just
like
instantiating
and
it
says
like
putting
it
into
the
global
and
then
putting
it
into
the
module.
But
for
some
reason
the
way
I
was
wiring
it
up.
It
wasn't
actually
available
on
the
global
and
it
wasn't
getting
required
and
then
it
was
3:00
a.m.
and
there
was
a
screw.
H
This
and
I
shot
my
laptop
and
then
I
just
have
not
motivated
myself
to
ever
open
it
again.
So
I've
mostly
been
a
lot
off,
for
instance,
but
yeah
I,
guess,
like
the
biggest
blocker
there
was
that
last
little
bit
of
like
we
had
wired
up,
there
was
just
something:
I
was
doing
wrong.
I
bet
you.
If
we
sat
down
and
looked
at
it
for
two
seconds,
joy,
your
Hannah
or
someone
who's
more
familiar
with
some
of
the
internals
of
food
would
probably
like
you
just
need
to.
B
G
B
G
A
I
Yet
it's
an
important
point:
it
is
in
our
implementation
of
fetch
all
right
if
we're
not
compliant
with
spec
r.
We
can.
We
actually
say
we
are
implementing.
Such
we've
had
some
arguments
within
the
core
around
the
platform
api
compatibility
that
it
either
it
has
to
work
the
same
exact
same
way
that
it
is
in
the
browser
or
it's
not.
You
know
we're
doing
something
wrong
because
it
for
the
promises,
some
other
things.
So
one
of
my
concerns
is
if
we
do
implement,
implement
exactly
what
the
API
like.
I
We
can
make
modifications
to
it
so
that
it
works
better
at
a
node
right.
What
kind
of
issues
arenal
run-ins
with
the
differences
there
in
brother?
So
to
avoid
that,
we
really
should
be
looking
at
it
going
back
to
the
web
MIDI
team
and
trying
to
propose
some
Chinese,
such
as
making
make
fish
or
whatever
API
here
Oregon
standards.
C
C
C
H
B
H
G
H
You
make
an
ad
option:
the
name
of
the
option-
that's
the
like
variable.
You
declare
the
variable
here
so
experimental
fetch
false
by
default.
Then
inside
of
each
to
be
here,
you
can
just
from
internal
options.
You
can
call
get
option
value
and
then
get
option.
Value
of
like
the
option
itself
will
then
give
you
these
flat
like
the
flag
that
you
passed.
So
that's
kind
of.
How
do
you
make
flags
in
note
now
which
was
fairly
straightforward?
H
H
G
H
See
in
a
second
I,
don't
even
remember
writing
this,
so
but
then,
essentially
all
we
do
is
like
we
check
the
option
value.
If
it's
true,
then
we
require
internal
fetch,
which
in
turn
that
requires
depth
of
fetch
and
then
it
just
defines
the
property
I
defined
it
on
HTTP.
So
this
was
one
way
that
I
thought
we
could
fix
some
of
the
problems
of
at
least
people
and
not
being
happy
that
it's
called
fetch
because
it
would
be
HTTP
dot
fetch.
So
it
would
be
part
of
our
HTTP
API.