►
From YouTube: Insights from Help Repo
Description
OpenJS Foundation Collaborator Summit, Berlin, 2019
A
Okay,
so
good
afternoon,
thanks
for
joining
this
session,
the
whole
idea
of
insight
from
Phil
purple
is,
to
you
know,
look
at
the
usage
Catalan
as
well
as
patterns
on
the
problem
which
user
are
encountering
when
they
make
use
of
the
audience
and
what
are
the
type
of
problems
which
they
owed
me?
Tetrapod
and
C
are
what
we
can
do
as
a
team
to
discuss
those
things
at
high
level.
A
You
can
see
there
is
a
lip
trend
that
is
happening,
and
if
there
is
any
things
we
can
do
at
the
design
level
at
the
code
level
or
at
the
documentation
level
back
in
the
cool,
so
that
the
overall
user
experience
is
improved.
So
that's
the
whole
of
ideas,
I've
been
spending
some
time
on
it
and
provoked
for
the
last,
maybe
one
under
fiercest.
So
couple
of
caveats,
these
are
my
personal
observations.
Not
necessarily
representing.
Can
you
group
for
the
project,
Aztec
poll
and
then
I
propose
is
a
running
report.
A
That
means
all
the
years
there
have
been
hundreds
of
issues
I'm,
not
representing
all
the
issues
as
such
the
ones
which
came
across
me
once,
which
I
was
part
of
you,
no
problem,
declination,
etc
are
the
one
which
are
a
person
directly
and
then
I
recommendations
against
each
of
the
issues
for
each
for
the
problem
patterns
again,
those
are
not
necessarily
hard
bound
or
final
recommendations.
I
just
put
some
some
observations,
as
based
on
my
understanding
as
a
team.
B
A
Expectation
was
that
we
look
at
that
as
a
baseline
and
then
apply
some
collective
intelligence
and
see
what
so,
that's
the
whole
idea.
Then,
let's
look
at
the
first
one
against
each
other
problems.
I
guess
I
have
four
of
them
at
high
level.
Each
of
them
I
have
the
problem
and
the
root
cause
and
the
combination
so
NPM
and
nor
installation,
reinstallation
and
uninstallation,
or
migration
reinstallation
of
migration.
This
is
by
far
the
most
common
issue
which
we
see
across
the
board,
without
any
exception.
A
So
if
you
have
100
open
issues,
you
see
around
40
of
them
belonging
to
this
cattle.
That's
it
that's
a
very
conclusive
scenario.
So
what
is
the
problem?
Problem
means
users
are
not
able
to
install
node.js,
probably
the
exceptions
they
get
file
not
found
or
some
weekly
level
crashes
or
things
like
that,
then
the
notable
upgrade
they
had
a
valid
healthy,
nor
installation.
But
when
it
comes
for
creation,
it
breaks
in
very
strange
man
and
then
uninstallation
again.
Either
installation
is
not
complete
or
it
leaves
some.
A
You
know
files
in
the
filesystem
exit
and
they
get
this
sort
of
exceptions
as
well
when
it
comes
to
NPM
all
the
things
which
apply
for
the
node.js
installation
apply
as
it
is
in
addition
to
that,
a
number
of
other
issues
like
proxy
failures,
network
connectivity
failures,
the
mismatch
of
the
version
between
Noren
and
PM
and
all
sort
of
things,
so
I
would
say.
Enfield
installation
issue
is
by
far
more
problematic
damages
related
issues.
A
At
high
level,
I
will
classified
into
one
is
the
one
which
has
a
native
installer,
something
like
that
get
or
increase
my
voice.
The
second
classification
is,
the
distributor,
has
a
custom
installer,
something
like
the
one
which
official
node.js
community
delivers,
which
has
an
MSI
installer,
something
which
is
associated
with
that
the
native
installer
versus
custom
installer.
Now,
if
you
install
node.js,
say
version
10
using
the
native
installer
and
then
you
want
to
install
or
upgrade
node
version
to
11
of
12
using
it
another
installer.
Then
there
is
no
coordination
between
these
installers
about.
A
A
And
if
there
is
a
native
component
in
that
you
build
it
using
the
build
tool
chain
and
then,
finally,
in
in
that,
in
that
sequence
of
operations,
there
were
the
n
number
of
expectations
that
could
fail.
For
example,
the
version
of
node.js,
which
the
food
figures
out
is
not
necessarily
the
mode
that
is
prevalent
in
the
system
and
things
like
at
high
level.
I
will
classify
that
in
two
one
is
resolution
of
the
NPM
script
itself.
As
we
know,
NPM
client
is
a
Java
Script.
A
A
Then
the
MU
CLI
dot
J's
in
turn
results
the
North
executing
itself,
because
the
first
line
in
BNP
MC
Lyte
of
J's
these
she
Bank
and
which
means
you
are
responding
back
and
then
this
multi-level
in
solution
can
go
for
a
toss
like
that
would
be
one
of
the
main
cost.
My
opinion
about
anything
installation
of
insulation
failure.
I,
absolutely
no
idea
have
no
idea
about
what
are
the
steps
that
are
involved
in
the
NPM
CLI
approaches
to
making
you
the
combination.
But
in
my
opinion
the
installation
should
be
standardized
across
all
the
distributors.
C
A
A
A
Normalized
or
you
know,
recorder
in
in
proportion
with
the
actual
activity
or
its
nature,
that
is
being
answered.
So
that's
the
key
thing
I
wanted.
Then
I
have
no
idea
about
who
owns
the
NPM
clients
I,
believe
there
is
not
stream,
but
I,
don't
see
anybody
raising
a
PR
or
addressing
an
issue
assets.
We
always
download
the
upstream
and
bundle
images.
C
D
D
D
B
A
Then
I
guess
good.
The
most
only
thing
that
we
should
be
looking
at
is
NPM
phones,
they
can
be
inclined,
but
the
issues
are
the
problems.
That's
coming
from
the
history.
Asian
is
always
reporter
against
larges,
so
either
we
should
have
a
documentation
on
it.
As
practice
that
says
it
should
all
gangrene
director
order,
or
we
should
have
a
better
scale.
A
poem
on
ships
will
be
implying,
Oh.
D
E
B
C
E
B
C
F
E
A
C
C
E
C
A
So
it
will
be
a
good
idea
to
look
at
tooling
as
an
option
to
redirect
the
issues
to
NPM,
but
then
P.
My
question
would
be
if
the
open
concept
or
the
the
whole
process
of
addressing
issues
in
the
Indian
community,
if
it
is
totally
different
than
the
inclusiveness,
the
openers
and
activity
activeness
of
the
newest,
and
eventually
there
is
a
gap.
Do
you
use
experience
in.
C
An
ideal
world
work
with
the
community
with
the
interaction
with
let's
say
it,
because
I
know
NPM
actually
closer
issues
on
yeah.
If,
if
they,
you
know
under
that
or
like
some
other
method
to
do
that
on
github,
what
would
that
look
like
to
you
to
be
able
to
work
well
with
the
help
repo
yeah
so
I'm
curious
about
that
I.
A
If
I
were
owning
the
NPM
see
what
I
will
do
is
I
will
look
at
improving
the
logging
process
of
the
service,
VT
process
and
better
document.
If
you
remember,
we
have
a
very
clean
documentation
around
module
resolution,
I
mean:
do
you
look
at
the
node
modules
in
the
current
folder?
Then
you
look
at
the
parent
folder
like
that.
You
recursively
go
up
to
the
vertex
of
the
file
system
and
then
you
get
the
package
tour
Jason
or
there.
A
A
D
A
C
B
D
They
were
amiable
and
very
had
relationships,
but
we
sort
of
codified
it
as
we
need
to
be
communicating
on
a
regular
basis
so
that
we're
both
benefiting
from
each
other's
work
instead
of
sort
of
like
feeling
the
effects
of
somebody's
work,
whereas
with
NPM
we
have
sort
of
the
added
complication
have
prior
community
poor
community
relations
between
and
Damned
folks
and
the
rest
of
the
project
early
on
the
new
projects.
Some
of
the
contributors
were
much
more
forceful
and.
B
D
B
D
A
Don't
get
excited
up
so
what
that
essentially
means
that
if
your
spawn
your
child
process
and
then
it
says
more
learning
process
like
a
CLI
or
a
tool
that
just
brings
a
piece
of
information
just
exits
so
because
the
controller
of
log
is
a
synchronous,
the
main
process,
the
main
child
process
do
not
really
pay
for
the
things
going
to
be
completely
flushed
out,
and
it
comes
back
to
the
parent,
essentially
using
the
data.
So
this
has
been
ever
since
I
can
remember.
I
joined
the
project.
A
By
seeing
this
issue
and
on
and
off
we
we
get
people
complaining
about
that.
We
know
the
problem.
What
it
is
we
know
how
to
solve.
It
is,
but
there
are
side
effects.
There
are
known
solutions
which
have
more
severe
side
effects.
Then
the
advantage
can
bring
about,
etc,
but
there
are
one
or
two
options
which
I
believe
is
something
which
we
can
look
at
to
solve
this
once
and
for
all.
A
Race
conditions
with
spawn
is
basically
again
in
design
level
issue.
When
you
spawn
the
child
process
up
to
some
point
in
the
protocol,
the
child
do
not
exist,
which
essentially
means
all
the
issues
that
stunning
all
of
these
point
sequence
is
thrown
back
to
the
border
in
a
synchronous
manner
and
the
moment
the
child
comes
into
life,
then
any
issues
that
is
coming
to
the
process
which
is
just
got
on
cannot
be
passed
back
to
the
caller
in
a
synchronous
manner,
because
it's
running
as
synchronously
the
child
is
completely
independent.
A
A
synchronous
era
back
you,
the
parent,
so
what
that
essentially
means
is
when
you
are
spawning
a
process
based
on
where
that
issue
happens,
the
caller
should
be
prepared
to
catch
the
error,
either
in
a
synchronous
manner
or
in
unison,
and
if
you
don't
have
enough
insight
about
what
type
of
problems
you
are
expecting,
unexpected
issues
can
happen
in
the
consumer
side.
So
that's
a
pretty
tricky
thing.
A
A
Essentially,
what
you're
doing
is
just
replicating
the
whole
node.js
process
in
the
China.
At
this
pace
and
depending
on
how
much
memory
the
child,
the
parent,
has
been
using,
say
2,
GB
or
3
to
be,
for
example,
you
are
allocating
as
much
of
memory
for
the
child,
basically
causing
a
more
of
Emmanuel
important
ratios.
A
There
could
be
a
better
capability
than
the
memory
footprint
replication
and
one
class
of
customers
can
get
affected
because
of
this
LS
specially
running
things
in
cloud
deployment,
for
example,
Emily's
charged,
and
then
this
particular
way
of
showing
things
can
potentially
cause
issues
for
the
consumer.
So
the
recommendation
is
look
at
ways
to
spawn
the
child
in
a
customized
manner,
depending
on
either
the
deployment
scenario
or
the
type
of
child
is.
C
A
C
A
The
child
process,
but
at
the
time
of
this
fourth
yeah,
does
it
require
any
memory.
Yes,
I
process,
the
ROS
organically,
based
on
its
memory
demand,
which
we
anyway
need
fresh
piece
of
month.
It
cannot
make
use
of
the
parents
only
entities
there,
for
example,
the
parent
is
1gb
and
the
child
is
going
to
be
n.
The
1gb
replicator
into
the
child
is
of
no
use
to
the
child.
It
has
anyway
allocate
new
energies,
so
essentially
the
1gb
of
patent
memory
becomes
useless
to
the
child
and
it
becomes
normal.
The
closest
is.
A
A
Means
you
know
using
more
from
an
existing
native
application.
That
means
you
don't
use
no
THC
or
the
nor.
Finally,
as
it
is
instead
of
having
the
your
own
native
process,
which
is
learning
a
major
chunk
or
a
larger
chunk
of
your
work,
your
and
you
just
want
to
make
use
of
node
for
a
specific
subset
of
your
workload,
say,
for
example,
an
animal
pound
or
a
interactive
work,
your
message,
so
the
problem
which
we
see
is
that
the
Emperor's
do
not
know.
How
do
you
consume,
though?
A
What
is
the
entry
point
to
and
what
are
the
things
which
you
need
to
finish
like?
What
are
the
things
which
you
as
an
embedded
and
customized,
and
what
are
they
control
flow
points?
What
are
the
two
novels
Dexter?
So
if
you
look
at
the
main
file
that
you're
you
Clemens
for
its
amplifon,
which
is
more
LCC
or
more
named
of
CC,
you
see
at
least
three
of
the
three
start.
Functions
for
elite
functions,
one
main
function,
so
basically,
these
are
entry
points
which
have
different
types
of
abstractions,
one,
for
example.
A
One
start
function
takes
the
whole
argument
as
it
is
for
your
input.
Another
init
function
rates
or
another
start
function,
takes
as
subset
of
that.
Instead
provide
you
with
the
flexibility
of
defining
the
inspector
or
defining
the
v8
engine,
or
the
isolate,
and
things
like
that.
So
essentially,
you
have
five
or
six
discrete
api's
to
call
and
control
the
sub-modules
approaches.
This
is
good,
but
if
you
can
it
confuses
people,
you,
don't
you
don't
necessarily
have
five
or
six
discreet
use
cases
for
embedding.
A
A
It
will
just
go
by
what
a
node.js
is
providing
as
it
is
capability
and
again,
if
you
are
embedding
node
Z,
this
you're
going
to
necessarily
need
to
control
the
v8
engine
as
it
is
so
the
whole
idea
is
either
talk
to
the
embedding
users
or
you
know,
plugins
feedbacks
and
then
look
at
one
of
the
two
or
three
discrete
way
of
embedding
no
J's.
You
find
it
expose
the
entry
points
and
then
document
at
this
point.
One
of
the
main
pain
point
is
there
is
absolutely
no
documentation.
A
C
A
So
I
know
IDM
we
have
a
product
called
I.
Iv
I
gave
information,
IBM
integration
bus.
So
in
that
it's
a
messaging
system,
we
have
Gulf
legacy.
Data
is
coming
from
the
mainframe
and
we
give
me
the
cue
and
things
like
that.
So
this
is
a
very
grain.
Api
is
so
I
grind,
Tara
flow,
that's
happening
and
then
based
on
the
type
of
the
message.
If
it
is
a
synchronous
we
passed
on
to
load,
so
there's
a
there
is
a
way
of
embedding
node.
A
C
Of
the
so
I
mean
I
actually
or
all
the
other
chuckling
a
lot
of
this
stuff
I'd
honest,
but
would
it
be
helpful
for
people
to
like
he
said
through
the
recommendation?
Would
it
be
helpful
to
like,
as
someone
who
doesn't
understand,
C++
at
all,
would
it
be
helpful
to
kind
of
go,
build
up
the
structure
of
that
and
allow
people
to
go
Oh
or
would
it
be
or
would
that
be
kind
of
my
list
of
like
hey?
We
have
this,
but
there's
no
content.
C
A
A
I
would
say
this
is
not
a
pattern
assets
from
the
health
before,
but
it's
it's
anybody
who's
working
on
ever
recurring
pattern
of
problem
statement.
People
complain
that
the
event
say
X
given
is
occurring
after
why?
Even
as
I
was
expecting
Y
to
be
happy
first
and
vice-versa,
and
this
one
keeps
keeps
it
we
keep.
Okay,
the
x
and
y
can
be
P
and
Q,
but
every
time
we
see
the
life
cycle,
events
or
the
screen
are
completely
coming
in
between
and
then
transform
stream
strings.
A
I
see
quite
many
users
complaining
about
I
want
to
transform
the
particular
stream
in
the
particular
pattern,
but
I
don't
see
the
data
coming
out.
I
see
the
original
data.
That's
coming
out,
the
transformation
is
not
happening
or
the
particular
data.
Email
is
not
triggering
itself
and
multi-level
piping.this
like
a
pipe
beep,
I,
see
probably
the
most
common
use
case
that
has
a
and
B
piping
in
the
C
or
a
piping
unit,
B
and
C.
A
These
are,
you
know,
different
scenarios
of
so
not
necessarily
all
combinations
of
energy
said
man
it's
not
necessarily
because
there
is
a
severe
problem
in
the
node.js,
but
because
these
are
not
necessarily
or
you
will
define
as
valid
use
cases.
So
as
in
when
people
various
issues,
we
look
at
that
and
see.
Oh
okay,
there
is
a
there's,
a
specific
use
case
that
is
missing
and
we
pipe
in
together,
you
see,
is
something
which
we
more
tima
vote.
Let's
implement
that
and
and
the
Caribbean
versus
well
I
am
not
sure
about
that.
A
But
fundamental
problem
is
that
the
stream
API
does
not
have
a
specification
or
not
just
like
any
API
will
have
a
well-defined
input
and
a
well-defined
output
document
and
the
design
follow
the
documentation.
All
the
documentation
follow
the
design
here.
The
the
fact
is
that
how
the
stream
works
becomes
the
expectation
or
that
becomes
the
document,
but
assuming
or
you
know,
keeping
in
mind
that
streams
need
to
work
with
a
number
of
other
processes,
probably
outside
of
node.js
as
well,
that
could
be
child
processors.
A
There
could
be
other
endpoints
coming
from
the
network
which
is
feeding
you
with
the
data.
Then
you
need
to
adhere
to
the
protocol.
That
is
to
find
out
the
other
end
point
or
you
need
to
align
with
that
expectation.
So
if
those
are
not
matching,
then
the
result
is
basically
the
toughest
are
our
lifecycle
events.
So
here
my
clear
recommendation
is
that
we
should
have
a
specification
by
specification.
I
mean
a
set
of
defined
principles,
set
of
expectations
about
how
the
exposed
API
should
work
in
any
sort
of
implement.
A
A
No,
this
is
basically
with
HPP
or
any
other
API
to
the
core
which
internally
make
use
of
scripts,
but
the
whole
point
is,
though,
you
are
making
use
of
a
core
screen.
The
data
control
is
building
the
application.
The
stream
will
not
control
the
databases,
the
velocity
at
which
the
data
comes
for
the
data
type
of
the
data
and
the
endpoint
from
which
the
data
coming
these
are
completely
in
the
control
of
the
application.
The.
A
Okay,
let
me
play
once
again,
so
we
have
a
stream,
which
is
same.
Basically,
you
are
making
us
an
HTTP
capability
and
as
an
HTTP
client,
you
know
that
there
were
spawns
coming
from
the
server
is
actually
a
stream.
Then
we
implement
a
callback
for
the
data
or
even
the
for
the
ending
end
of
the
finish
even
itself.
So
these
are
implemented
in
the
user
land.
The
core
bag
belongs
to
the
user,
whereas
the
Twitter
of
the
raiment
belongs
to
the
Pope,
so
use
it
as
a
user.
A
A
That's
pretty
much
I
have
so
just
to
reiterate
what
I
said
in
the
beginning.
These
are
not
necessarily
the
fault
is
in
the
DOJ's
support
report
as
important
they're,
probably
the
ones
which
I
believe
is
following
a
pattern,
and
then
we
also
looked
at
the
root
cause
and
what
are
the
recommendations?
Have
me,
some
of
them,
as
not
necessarily
will
work
as
it
is.
We
need
a
better
approach,
but
some
other
things
which
we
know
what
can
be
done
in
a
systematic
manner.
A
Somebody
who
is
interested
take
ownership
champion
it.
Basically
ownership
not
necessarily
mean
implement
the
end-to-end
solution
for
that,
but
just
to
kick
start
the
conversation
in
in
cases
or
define
some
milestones
and
see
you
can
get
engaged
with
the
people
and
compelling
it.
Some
part
of
the
work
then
have
that
as
a
initiative.