►
From YouTube: Node.js Tooling Group Meeting
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
All
right
there
we
go
nice.
Well,
we
haven't.
This
is
a
sparsely
attended
meeting
of
the
node
tooling
group
going
into
labor
day
weekend,
which
might
be
one
of
the
reasons
just
looking
at
our
chat.
I
don't
see
any
additional
folks
in
here.
A
A
A
A
A
We've
got
some
updates
for
recruits
of
copy,
it
has
landed.
A
A
A
A
Yeah
I'll
just
put
a
link
to
the
docs
for
it.
I
guess
here
we
are.
A
A
That
that
all
of
the
file
system,
operators
in
node.js
currently
accept
a
buffer
or
a
string
for
further
operation,
and
the
reason
for
this
is
some
edge
case
file
systems
and
I
believe
unix,
linux,
linux
or
unix.
A
A
Someone
was
saying
it
had
to
do
with
utf-8
string
encodings,
but
that's
weird
to
me
because
I
think
node.js's
strings
work,
fine
for
utf-8
and
coding.
So
I'm
not
I'm
not
sure
of
the
exact
edge
case.
James
snell
said
it
had
to
do
with,
like
some
edge
case,
japanese
character
set
actually
but
said
it
had
come
up
for
utf-8
at
some
point,
so
we've
shipped
copy
without
support
for
buffer,
because
there
was
no
good
way
to
it.
A
Does
a
bunch
of
path
operations
to
do
the
copy,
like
joins
paths,
resolves
paths,
slices
paths
while
it's
copying
the
entire
directory
structure
from
point
a
to
point
b
and
we
node.js
doesn't
have
a
built-in
api
for
performing
path
operations
on
a
buffer.
A
So
what
would
be
in
the
buffer
in
this
case?
Would
it
be
like
the
source
or
destination
directory?
Yes,
it
would
be,
it
would
be
the
source
and
the
destination.
You'd
have
to
keep
it
a
buffer,
the
whole
time
and
then
the
buffer
would
potentially
have
like
unicodes,
it's
like
say,
16
characters
in
it
as
an
example.
So
so
maybe
the
buffer
is
utf-16
and
it
never
gets
turned
into
a
string.
A
So
I
have
it
about
80
percent
done
cool,
that's
great
that
so
recursive
copy
is
experimental
right
now.
It's
experimental
yeah!
Yes,
but
it's
my
hope
by
getting
this
thing
built.
I
can
then
use
it
as
a
case
to
it
kind
of
checks
off
that
one
thing
james
snell
said
what
he
would
require
to
be
able
to
call
it
not
experimental
right,
but
it's
a
giant
pain
in
the
neck,
because
I've
been
having
to
like
basically
I've
I've,
just
ported
the
path
api.
A
A
utf-8
is
the
exact
same
as
ascii.
If
it
says
slash,
so
you
don't
have
to
do
like
the
same
stuff
for
for
unicode
for
for
utf-8.
A
A
A
A
A
A
A
A
This
is,
I
shouldn't
talk,
I'm
I
don't
know
this
topic
too
well,
so
I
won't
go
too
deep
on
it
yeah
inside
there,
but
but
tldr.
We
need
to
be
able
to
handle
the
buffer
to
get
that
work
over
the
finish
line
right
all
right,
I
mean
the
only
thing
I
don't
like
is
it?
The
only
thing
I
don't
like
is:
it
adds
like
a
thousand
lines
of
code
to
the
code
base
right,
but
that
does
seem
like
potentially
a
useful
thing
in
general
yeah
like
like.
A
Our
our
implementation
of
rim
raft
wouldn't
work
in
utf-16
buffers.
Basically,
even
though
it
does
work
on
buffers
interesting,
okay,
yeah,
so
I
mean
that
potentially
seems
like
a
useful
thing
in
general
to
have
in
in
node
yeah,
and
I
also
think
there's
like
a
there's
a
join
helper
somewhere
in
node
that
works
on
buffers,
but
I'm
not
sure
where
it's
actually
used
in
the
code
base,
but
we
can
actually
delete
that
because
the
other
implementation
is
only
a
partial
implementation
as
well.
A
A
It's
cool
that
you've
made
some
some
good
progress
on
it,
though
sports
map
v3.
Should
we
just
look
if
there's
any
more
new
bugs
open
for
it
sure.
A
I
forget:
why
did
we
decide
to
leave
that
on
the
agenda?
There
was
a
reason.
A
We
could
probably
get
rid
of
it
if
we
just
want
to.
I
mean
I
mean
it's
open
question:
do
we
want
to
leave
our
old
feature,
work
open
and
just
try
to
triage
bugs
for
it?
Each
meeting
I
feel
like
that
could
be
worthwhile
potentially
yeah
is
there.
I
wonder
if
there's
a
better
way
to
do
that
other
than
just
leaving
it
kind
of
permanently
on
the
agenda,
but.
A
A
A
Nothing!
New!
There!
Okay
argument,
parsing
yeah,
it
sounded
like
so.
In
slack
joe
mentioned,
he
hadn't
had
a
chance
to
do
any
work
there,
and
neither
have
I
been
focused
on
create
react
app.
Lately
we
need
to
perhaps
rope
someone
else
in
yeah.
That's
not
a
bad
idea.
A
There
you
see
how
joe's
feeling
once
he
on
once,
I
know
how
exciting
it
is
to
switch
into
doing
management
so
yeah,
maybe
he'll.
He
did
say
you
know
he
may
have
more
time
in
the
near
future,
once
he's
on
board
at
some
people,
yeah
google's
in
the
middle
of
our
perf
cycle,
so
I'll
start
to
have
more
resources
again
in
a
week
or
two
okay,.
A
New
business
there's
a
little
bit
of
new
business.
Oh
okay!
There's
this
really
there's
this
kind
of
interesting
bug
open
on
node.js
right
now
for
rimraff.
A
A
A
A
Yeah
like
my
default
os
x,
is
2560
files
so,
like
I
feel
like
we
would
be
hearing
about
this
bug
a
lot
more
often
if
it
was
doing
it
in
the
general
case.
A
A
A
I
think
the
the
process
would
be
happening.
The
process
is
just
running
on
zip,
so
it's
not
it
would.
I
doubt
it
would
be
holding
any
file
handles
or
it
shouldn't
be
no,
but
I
mean
like
like
so
it
I
think
once
oh
yeah,
I
guess
I
guess
that's
right.
The
sub
process
would
run
unzip
and
then
finish
and
then
call
a
callback
which
would
do
the
rm.
A
A
A
Still
the
rm
command
does
the
non-recursive
version
just
call
through
to
fs
like
what
is
unlink
or
something
I
don't
think
it
does.
I
think
we
use
the
like
rim
raph
logic,
always
why
would
it
be
even
doing
the
deleted?
Then,
though,
should
only
be
deleting
oh,
it's
just
deleting
that
yeah
in
this
case
would
just
be
deleting
the
zip
file
right,
yeah.
So
yeah
he's
just
trying
he's
trying
to
delete
a
single
file,
anyways
yeah
yeah.
A
A
For
some
reason,
I
thought
it
had
to
do
with
deleting
a
large
number
of
files,
but
it
doesn't
seem
like
it
does
have
to
do
with
it.
It's
like
literally
single
files
that
are
having
an
open
file
handling
right.
I
wonder
if
that's
the
issue
like
it's,
if
you
just
delete
a
single
file
with
it
without
even
being
in
this
callback,
and
maybe
that's
a
problem,
because
that's
not
really
the
normal
use
case
for
this.
A
You
know
what
he's
using
to
come
up
with
these
names
for
these
zip
files,
because
it
could
be
like
if
there
was
a
collision
on
file
name
right.
But
if
you
look
at
the
I
don't
know,
if
the
name
in
the
lsof
output
is,
is
the
actual
file
name
but
they're,
just
like
huge
random
strings,
yeah
exactly.
A
All
right
not
much
to
do
here,
we're
gonna
have
to
debug
it
on
the
call
yeah
anyways
interesting
I'll,
see
if
there's
something
to
happen,
yeah
yeah!
Well,
that's
everything
on
my
mind,
yeah,
that's
pretty
much!
All
I've
got
as
well
all
right.
I
might
go
back
to
trying
to
collect
some
metrics
for
my
team,
then
trying
to
get
a
dashboard
built
all
right.