►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
sorry
I
couldn't
be
there
today,
but
I'm
going
to
present
by
the
magic
of
the
Internet.
My
name
is
Andrew
nice
to
meet
you
I'm,
a
package
manager
of
researcher
I've
been
working
with
the
ipfs
team
for
a
few
months,
specifically
on
working
out
how
my
PFS
can
help
with
making
package
management
better.
Today,
I'm
going
to
talk
about
decentralized
package
management
using
IP
FS,
and
this
is
a
hard
problem.
There
are
a
number
of
difficult
parts
involved
in
doing
decentralized
package
manager.
Today,
I'm
going
to
talk
about
decentralized
dependency
resolution.
A
This
basically
stems
from
some
research
that
I
did
into
looking
at
how
the
challenges
involved
in
decentralized
publishing
which
to
kill
a
long
story
short
shakes
out.
As
when
publishing
a
package
in
a
decentralized
system,
you
need
to
be
publishing
all
of
the
dependencies
of
that
package
alongside
it.
A
That
you'd
need
to
be
able
to
just
install
a
single
package,
and
you
can
make
many
of
these
and
publish
them
straight
to
your
IP
FS
and
actually
take
control
of
how
you
work
with
packages
rather
than
relying
on
a
centralized
registry.
I've
made
a
handy
little
command-line
tool
that
makes
it
really
easy.
This
one
works
for
NPM,
but
it
should
work
in
a
similar
fashion
for
other
package
managers
too.
So,
let's
check
it
out.
A
A
A
Let's
keep
going.
We
can
also
publish
something
directly
from
the
NPM
registry.
Let's
publish
react,
so
that's
published
the
latest
version
of
react,
which
is
sixteen
point
eight
point:
six.
We
can
just
copy
and
paste
that
run
that,
and
we
have
just
installed,
react
straight
from
ipfs
completely
self-service.
We
can
also
publish
older
versions
of
react.
Maybe
react
fifteen
there
we
go
just
install
that
from
there
and
you've
got
a
previous
version.
The
cool
thing
that
you
can
do,
then,
is
actually
merge.
A
Those
two
registries
we
created
together
to
create
a
single
registry
that
contains
both
of
those
versions.
Let's
check
that
out
on
the
Gateway
and
see
what
it
looks
like
there
we
go.
We
have
two
different
versions
of
react
with
all
the
dependencies
to
be
able
to
install
those
together,
and
this
is
composable,
so
you're
able
to
just
keep
composing
different
micro
registries
together,
creating
new
registries
as
you
go
and
being
able
to
successfully
resolve
those
dependencies
over
IP
FS
without
any
centralized
registry
required.