►
From YouTube: SES Meeting: Hardened Babel
Description
Nicoló Ribaudo of Babel gives us some help improving SES’s use of Babel.
A
All
right
welcome
to
the
cess
meeting.
This
is
march
2nd
and
today's
agenda
is
to
discuss
babel
and
compatibility
with
hardin
javascript,
and
we
have
nicolo
and
michael
nikolo
being
the
expert
on
babel
and
michael
being
expert
on
our
use
of
babel
categoric
for
our
emulation
of
hardened
javascript
and
we
use
in
the
in
the
ses
shim.
A
We
use
babel
to
do
an
esm
to
program
transform
in
order
to
build
out
a
compartment
as
a
third-party
module,
loader,
and
and
because
of
that
we
need
babel
to
run
in
a
hardened
javascript
environment
and
at
the
moment,
what
we're
doing
to
make
that
possible
is
for
one
we're
using
babel
standalone.
And
I
don't
remember
the
reason
why
we're
doing
that.
A
We
have
to
initialize
babel
standalone
at
the
application
layer
before
we
lock
down.
Otherwise
it
can't
initialize
because
it
finds
frozen
because
of
the
property
override
mistake
now.
So
that
has
an
obvious
fix.
We
go
into
the
buffer
shim
and
get
a
change
committed
upstream.
That
changes
various
assignments
into
defined
property
calls
and
michael
did
some
work
over
this
weekend.
That
has
greatly
improved
our
compatibility
with
babel
by
doing
a
custom,
build
of
babel
standalone
and
a
fork,
but
running
a
fork.
Long
term
isn't
really
tenable
from
a
maintenance
perspective.
B
B
B
However,
you
might
have
to
check
in
our
build
process
how
exactly
to
build
bubble
core,
because
there
are
some
like
variables
that
might
need
to
be
right,
overwritten
in
order
for
it
to
work
in
the
browser
we
have
some
files
like
for
some
files.
We
have
the
browser
and
the
node
version,
so
you
have
to
make
sure
that
it's
everything
is
bundled
correctly.
The
alternative
is
to
not
use
bible
core,
but
to
use
bible,
parser,
bible,
traverse
and
bible
generator,
which
are
the
three
main
steps
that
will
corrupt
internally.
B
C
B
C
C
Then
just
made
some
changes
to
the
buffer
shim
and
it
was
then
it
was
okay,
but
I
I
know
that
in
another
part
of
our
code
we
are
just
using
babel,
traverse
and
parson
generate
and
yeah.
That's
probably
the
best
way
forward.
I'm
not
sure
why
we
ended
up
doing
the
standalone
stuff.
I
I
think
it
was
because
we
we
yeah.
I
don't
even
know
why.
A
But
yeah
we
we
could.
I
have
looked
into
this
into
the
pa
in
the
past,
trying
to
just
use
the
the
three
components
based
off
michael.
Ultimately,
you
built
both
of
these
the
the
version
in
in
sas
and
the
version
in
agorik
sdk
for
doing
transform
for
other
for
the
evasive
transforms,
and
I
I
suspect
that
it
is
possible
to
just
use
the
three
components
and
avoid
using
core.
C
B
B
D
A
A
B
D
I'm
also
wondering
one
of
the
reasons
we
remove
the
transforms
and
things
like
that
that
usually
pulls
in
regenerator
and
and
other
shins
which-
and
I
believe
the
one
of
the
reasons
we
want
to
avoid.
Those
well
on
top
of
not
running
transform
code
is
because
they
often
trigger
the
override
mistake,
and
I
I
suppose
maybe
that's
also
something
we
should
try
to
fix
upstream,
or
am
I
mistaken?
There.
B
B
D
I
think
I
also
have
more
of
a
curious
question.
Curiosity
question:
I
find
a
lot
of
projects
that
end
up
pulling
in
the
generator
transforms,
and
maybe
it's
a
mistake
in
their
target
preset
on
configuration
or
I'm
not
sure,
but
it
it
feels
like
a
lot
of
projects
end
up
pulling
in
those
transforms
when
they
don't
really
need
to
and-
and
I'm
actually
curious
how
the
community
or
bible
is
steering
the
community
towards
avoiding
doing
that.
B
We
have
made
some
changes
in
the
past
year
that
make
it
more
like
we
had
some
blog
post
about
possible
organizations
and
we
moved
the
targets,
option
to
be
used
more
and
to
be
more
visible,
so
people
are
monetizing
it
more
and
also
in
bubble.
8.
We
will
change
the
default
value
of
targets
to
be
whatever
browsers
list.
The
finance
like
not
that
browsers,
rather
than
just
everything
down
to
s5.
B
B
A
That
I
hesitated
to
up
almost
I
mean
I
wrote
this
module
called
queue
a
really
long
time
ago,
and
I
have
hesitated
to
upgrade
it
at
all
ever
because
because
or
like
to
use
esm
syntax,
for
example,
because
everything
that
you
do
like
that
limits
is
is
potentially
a
breaking
change.
And
I
found
that
breaking
q
is
very
dangerous.
A
B
Well,
I
mean
for
liberty,
for
libraries
is
no,
it's
not
uncommon
to
just
target
the
latest
lts,
not
js
version.
At
the
point
of
the
last
major
release
like
there
are
some
libraries
that
support
everything
from.
I
know
not
0.10
or
something
like
that,
but
yeah
from
what
I've
seen
outside
of
people
involved
in
d59,
most
library,
authors
just
target
the
latest
lts
version
yeah.
C
A
Wait
so
most
of
the
all
my
all
of
the
documentation
on
babel
is
framed
in
terms
of
core
right.
Is
there?
Is
there
a
a
piece
of
documentation?
Maybe
you
could
help
us
find
a
piece
of
documentation
on
how
to
use
these
components
piece
wise.
That
would
be
helpful
to
me.
I
know
I
know
that's
probably
where
I
ran
out
of
gas
on
this.
B
B
There
is
a
good
document.
It's
they
called
the
plugin
handbook
that
defines
like
all
the
internal
build
traverse
api
and
not
all
the
internal
but
the
the
most
important
internal
api.
I
don't
think
that
the
like
external,
like
entry
point
of
bubble,
traverse,
is
actually
documented,
but
most
of
what
you
will
need
is
there.
A
C
B
I
mean
by
default
we
enable
all
this
table
syntax.
We
had
in
the
past
an
option
to
enable
all
the
proposals
by
default,
but
there
are
proposals,
they're
not
meant
to
be
stable,
so
we
we
removed
the
option
at
some
point,
so
stable
syntax
will
always
be
enabled
by
default.
If
you
want
to
use
proposals,
you
have
to
choose
what
you
want
and
what
you
don't
want.
B
B
B
A
A
Well,
this
was
the
only
topic
for
today
and
I
think
that
we've
spent
it.
We
have
we
like
again,
we
have
our
homework
to
do
to
see
if
we
can
make
any
progress
and
then,
of
course,
and
then
to
recap,
we
also
have
your
invitation
nikola
to
put
together
a
pr
to
to
to
test
babble,
at
least
to
the
part
at
least
the
three
internal
parts
in
the
context
where
there
are
more
not
frozen
primordials.
C
B
A
Are
we
so
there
there
are
layers
of
support
for
cess
the
the
first,
the
first
layer
is,
can
you
use
it
at
all
in
in
an
environment?
That's
using
sets
the
the
second
layer
after
that
is,
can
you
use?
Can
you
initialize
it
after
lockdown
has
been
called
and
we're
confident
that
the
threes,
the
three
internal
components
of
bowel
work
under
those
circumstances,
the
third
layer
is,
can
you
load
it
in
a
compartment
which
is
to
say
with
with
only
the
shared
intrinsics?
I
do.
We
know
whether
we
can
do
that.
C
B
B
A
E
B
B
A
A
E
A
B
C
D
C
Opinion
on
formatting,
like
we've,
seen
recast
in
the
past
to
kind
of
provide
reduce
source
code
round
tripping.
If
there's
no
modifications
to
it,
but
they
don't
support
the
the
preserve,
retain
lines
option.
So
we
tried
hacking
it
up
to
make
it
work
better.
But
it's
there's
just
several
places
where
they
don't
use
it
in
the
same
portion.
B
C
E
E
It's
always
introduced
hazards
because
of
the
difference
in
the
actual
semantics
versus
what
the
code
looks
like
it's
doing.
The
the
standards
of
semantics.
Preserving
that
most
transformations
engage
in
is
not
semantics
preserving
for
us.
So
that's
that's
one
reason
why
we're
avoiding
source
maps
in
general,
because
we're
avoiding
any
kind
of
transforms
like
that
in
general,
the
particular
transform
we're
doing
we
very
very
carefully
designed
to
be
minimally
intrusive,
so
there's
large
sections
of
the
code,
basically
everything
without
an
importer
and
export.
C
B
How
much
would
be
custom
like
different
regarding
return
columns,
I
also
do
not
have
an
opinion
right
now,
like
an
alternative
option,
which
is
to
like
with
like
written
lines.
I
think
someone
already
asked
us
for
something
like
that
in
the
past
like
a
few
years
ago,
but
we
never
really
considered
the
like
the
feature
request,
but
I
I
I
don't
actually
have
an
opinion
on
this.
I
should
ask
to
the
rest
of
the
team.
C
As
far
as
the
the
only
yeah,
the
only
difference
that
I
would
see
is
that,
if,
if
there's
a
way
to
adapt
the
the
generator
where
it
actually
puts
things
into
the
buffer
to
compare
that
against
where
we
think
we
are
in
the
token
list
so
far,
that
would
that
would
be
a
very
cheap
way
of
getting
recast
like
behavior,
without
having
to
worry
too
much
about
the
abstract
in
the
ast
or
anything
like
that.
Just
be
the
token
less
that
we've
been
looking
at.
B
C
B
C
C
So
it
would
come
very,
very
close
if
not
perfect.
So
basically,
the
behavior
we'd
like
is
for
the
original
source
to
be
printed
and
where
we've
done
a
transform
to
either
emit
some
emit
some
tokens
with
spaces
or
else
insert
new
things.
At
the
end
of
the
line
that
are
written
out
concisely,
they
don't
have
to
be
formatted
in
any
way.
C
So
so,
basically,
it
would
preserve
all
the
front
parts
of
the
line
as
much
as
they
could
and
the
way
the
bible
token
list
works
is
it
has
all
the
tokens
that
were
parsed
in
order
with
source
line
and
source
column
attached
to
them.
So
we
have
all
the
information,
that's
necessary.
It's
just
a
matter
of
putting
it
together
in
the
generator.