►
Description
In this installment of the weekly discussion revolving around the latest news and topics on Microsoft 365, hosts – Vesa Juvonen (Microsoft) | @vesajuvonen and Waldek Mastykarz (Microsoft) | @waldekm, are joined by are joined by US based member of the Customer Engineering Team, PnPjs project owner, Patrick Rodgers (Microsoft) | @mediocrebowler. The trio discussed the latest release of PnPjs v3.0, the design theme, optimizations, how perception of open source is changing, the behavioral change needed to drive project success and more. Microsoft and PnP Community delivered 15 articles in the last week! This session was recorded on Monday, March 21, 2022.
References:
• See the full blog post for this episode at https://aka.ms/m365pnp/community/blog
• Download the podcast for this episode at http://pnpweekly.podbean.com.
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp/vide
A
And
action
and
welcome
everybody
bmp
weekly
episode,
158,
it
is
21st
of
march
2021,
one
more
week
to
go
in
the
first
quarter
of
the
year.
It's
pretty
cool
kind
of
spring
is
coming
or
summer
is
coming
now
in
the
bmp
vehicle.
We'll
talk
about
the
latest
on
microsoft,
365
and
we
have
typically
a
visitor
and
we
go
through
some
of
the
latest
articles
from
the
microsoft
and
the
community.
A
B
B
We
are
joined
by
no
one
else
than
patrick
rogers,
who
a
few
years
back
already
thought
about
building
this
javascript
sdk.
Apparently
that
is
being
used
by
a
few
people
across
the
world.
So
we're
going
to
talk
to
him
about
journey
that
he's
made
over
the
years
and
what
they
shipped
last.
I
guess
two
weeks
ago
already.
A
A
A
A
A
B
C
A
C
A
C
C
C
C
C
You
know
with
an
anniversary,
as
you
always
do,
and
so
it's
neat
to
think
back
on.
Like
you
know,
I
feel,
like
I
haven't
come
that
far,
but
also
have
come
quite
far.
So
it's
I
don't
know
trying
to
balance
that
out
of
you
know
how
I
feel
today
versus
how
I
would
have
felt
10
years
ago
about
where
I
am
today,
and
you
know
that
sort
of
feeling.
So
it's
it's
neat.
It's
good.
A
And
it's
always
when
you're
moving
across
the
organizations
from,
for
example,
consulting
services
to
engineering
role
and
all
of
that
those
are
kind
of
a
big
reset
moments
so
to
say,
especially
in
microsoft.
It's
it's
just
a
for
those
who
are
external.
They
don't
necessarily
understand
that,
but
at
this
completely
different
organs,
a
completely
different
world,
so
to
say
so,.
C
A
But
we've
been
working
together
regardless,
so
that's
good,
yeah,
that's
good,
but
now
the
one
thing
what
what
you
worked
like
from
a
start
or
well
you're.
The
creator
of
the
whole
thing
is
the
bmpjs
and
under
the
bmpjs
last
week
we
had
julie
on
the
show.
We
talked
about
the
release
of
three
and
we
talked
about
the
fact
that
there's
16
billion
requests
generated
by
by
bmpjs
in
february
2022.,
that's
absolutely
insane.
That
means
thousands
and
thousands
of
requests.
Every
single
second
initially
went
online
through
that
library.
C
C
Yeah
and
it
just
kept
kept
growing,
which
is
fantastic.
It's
been
it's
amazing
to
see
the
growth
and
the
support
it's
gotten
from
everybody
in
the
community
and
and
I've
said
it
on
various
other
calls.
But
it's
been
really
invaluable
as
to
have
julie
as
well
get
more
involved.
You
know,
with
v3
from
the
beginning
and
helping
to
design
it
and
and
having
somebody,
because
it's
we've
had
lots
of
community
participation
over
the
years,
but
we
haven't
had
somebody
sort
of
deeply
involved.
A
C
It's
probably
a
couple
of
things,
probably
a
combination
of
a
couple
of
things.
I
think-
and
this
is
obviously
it's
an
opinion.
So
you
know
lots
of
other
people
would
have
different
opinions,
but
I
think
the
fluent
interface
kind
of
design
resonates
with
people.
I
think
it
makes
things
easier
for
for
folks.
I
think
it
makes
things
a
little
clearer
than
some
other
things.
Obviously,
everybody
has
different
opinions,
I'm
not
trying
to
say
people
are
right
or
wrong,
but
I
think
that's
helped
a
little
bit.
C
I
think
we've
always
tried
to
be
very
responsive
to
feedback
and
issues.
So
as
issues
come
in,
we
try
our
best.
You
know
it's
it's
just
a
few
folks,
but
we
try
our
best
to
get
the
big
stuff
resolved
every
month.
Right,
we've
done
month
releases
for
six
years
now
I
think
we've
missed
two
or
three
over
six
years
monthly
releases.
I
think
that
you
know
regular
cadence
and
then,
when
we've
had
stuff
reported,
that
is
like
a
show,
stopper
kind
of
bug.
C
D
C
It
right
now
it's
it's
a
classic.
We
have
tons
and
tons
of
tests,
but,
like
you,
can't
really
automate
search
because
you
need
the
user
context
and
stuff,
and
so
we
don't
have
tests
for
search,
and
so
we
didn't
catch.
That
search
just
doesn't
work
right,
yeah,
which
at
one
point
it
worked.
I
know
because
we
sort
of
like
tested
it
just
like
a
couple:
quick
searches,
but
then
at
some
point
in
the
in
the
process
we
broke
it
and
never
caught
it.
C
So,
but
we
got
a
patch
release
out
real
quick,
so
I
think
stuff
like
that,
builds
trust.
It
shows
you
our
listening
and
I
think,
with
the
major
releases.
You
can
really
see
where
we've
gotten
great
feedback
from
people,
but
fundamentally
that
feedback
means
we
need
a
different
design
like
we
can't
take
your
feedback
and
just
like
yeah
tweak
it
and
done
it's
like.
Oh
that's,
great
feedback
and
man.
C
I
wish
we
could
do
that,
but
there
just
isn't
a
great
way
we'd
have
to,
and
so
you
see
that
with
v3
we
got
a
lot
of
feedback
about
folks
wanting
to
hit
multiple
sites
from
the
same
application
like
especially
in
node
folks
wanting
to
configure
requests
in
lots
of
different
ways,
and
we
didn't
have
great
ways
to
do
some
of
those
things
right.
So
we
kind
of
blew
it
all
out
and
you
can
get
at
that
stuff
now.
So.
B
Yeah,
so
you
said
that
pmp
yes
has
been
around
for
six
years,
ish
right
so
and
and
in
that
course
you
had
three
major
versions,
meaning
like
three
designs
in
a
way.
How
did
you
go
about
or
how?
How
did
you
experience
refactoring
things
at
scale
because
it
isn't
it
isn't
small
and
trivial
like
it's?
It
has
significant
surface
to
it.
So
how
did
you
go?
You
know,
like
you,
have
this
thing
that
works
and
it's
like
yeah:
let's
do
it
differently
and
then
you
kind
of
start
from
scratch.
Yeah.
C
I
so
there's
been
six
major
releases
because
we
were
a
long
time
ago
we
were
sp
pnp
dash
js,
I
think,
was
the
lane
of
the
library,
and
we
did
three
versions
there
and
then
we've
transitioned
over
to
the
pnp
github
organization,
so
we're
at
pnp,
sp
and
all
those
things.
That's
been
three
major
versions
now
there
so,
but
thinking
about
major
versions
for
me
is:
it
has
to
be
worth
it
right.
C
C
You
know
it's
a
thing
that
works
and
and
once
we
got
there
once
I
got
there
that
feels
pretty
good
and
then
you
think
about
how
to
refactor
everything,
and
one
of
the
things
we
did
very
consciously
in
v2
is
moved
to
a
pattern
that
separated
what
consumers
of
the
library
are
using
versus
what
the
internals
are
without
changing
the
internals.
Yet
right,
because
that's
was
too
much
work
at
once
and
I
didn't
know
really
what
I
wanted
to
do
with
the
internals
yet.
C
But
I
knew
at
some
point
because
they
hadn't
really
changed
in
six
years.
Just
about
there
have
been
some
small
changes,
but
it
was
time
to
do
something
big
there
and
we
in
v2
made
it.
You
know
factory
functions
and
interfaces
which
isn't
like
a
groundbreaking
software
design,
but
it's
a
very
effective
one
and
we
separated
the
stuff
that
way,
and
so
there's
a
big
change
to
everybody's
code
in
v2
and
then
for
v3.
C
We
were
able
to
completely
rewrite
the
guts
of
it
and
the
only
code
other
than
a
few
little
changes
here
and
there
was
the
setup,
the
initiation
of
the
library
from
there.
So
it
was
kind
of
thinking,
long
term
and
over
the
years
of
like
okay,
we
want
to
get
to
this
place,
but
we
can't
just
jump
there.
It's
too
much
work.
It's
too
much
change,
it's
too
much
churn.
So
how
do
we
step
through
that?
C
And
it
was
really
like
so
thinking
just
about
the
at
pnp
versions
of
the
library
like
v1-
was
really
like
get
over
to
the
at
pnp
organization,
and
if
you
remember,
the
sp
pnp
js
library
is
just
one
big
package,
and
so
v1
was
splitting.
That
package
up
right.
V2
is
interfaces,
factory
functions,
v3,
redoing,
the
guts
and
then
v4.
I
don't
know
something.
A
I'm
going
to
put
you
on
spot
on
a
question
which,
which
I
could
ask
for
myself
as
well,
so
this
is,
let's
say:
how
do
you
answer
this,
but
so
dmpjs
is
open
source
community
driven,
not
microsoft,
provided
you're,
microsoft,
employee,
but
it's
not
microsoft,
provided
it's
not
there's
no
sla
for
microsoft
and
no
support
for
it,
but
it's
still
being
used
by
thousands
tens
of
thousands
of
customers
every
single
month.
How
does
that
work?
Why?
Why
is
it?
In
other
words,.
C
E
C
You
know,
and
then
powershell's
got
folks
in
there
that
are
microsoft,
people,
but
they're
not
driven
or
owned
by
like
an
engineer
and
feature
team
right.
So
it's
it
kind
of
lives
in
this
gray
area,
because
it's
not
official,
it's
not
supported
you
know
other
than
by
the
community
and
by
those
of
us
working
on
the
different
projects.
You
know,
so
I
think
it
it's
not
official
but
again
I'll
come
back
to
over
the
years.
C
A
C
C
C
I
think
in
c
sharp
it's
doing
more
of
this
and
I
I
don't
know
much
python
or
go
or
these
languages,
but
I
see
them
growing
very
rapidly
and
in
the
same
manner,
everything's
very
open
and
you
can
contribute
or
report
issues
and
I
think
that's
sort
of
the
new
support
model
really
because,
like
think
about,
if
you
were
to
scale
that
to
microsoft,
just
imagine
somebody
might
be
trying
to
work
on
this
internally
and
you
get.
The
teams
can
actually
have
issues
lists.
C
They
get
feedback
directly
from
people
right
and
not
that
that
feedback
is
any
more
or
less
important
than
the
other.
But
you've
got
these
direct
connections
and
you're
building
that
trust
across
things.
And
so
I
think,
that's
you
know
how
you
say:
it's
not
officially
microsoft
supported,
but
it
is
supported
and
again
that
comes
back
to
that
track.
Record
of
like
monthly
releases
responsive
to
issues
like
we
are
supported
like
we
haven't,
released
it
and
it's
just
sat
there.
C
There's
no
issues
list,
there's
one
version
from
four
years
ago,
like
that's,
not
the
way
to
do
it
right,
and
so
it's
supported
and
we've
shown
it
supported
by
how
we've
maintained
it
over
the
years,
because
I
think
that
argument
was
much
more
valid
six
years
ago
when
we're
just
getting
started.
People
are
like.
Oh,
is
this
supported?
What
is
this?
C
B
And
we're
a
call
when
you
know
like
there
was
a
release.
We
would
all
get
per
post
a
bunch
of
msdn
dvds,
cds,
dvds.
You
know
we
would
install
the
preview
version
and
so
forth,
and
that
was
the
state
of
things
back
then
majority
of
the
tools
with
like
codeplex,
maybe
what
wasn't
even
around
yet
or
maybe
it
was
early
stage.
B
You
know
so,
like
the
whole
open
source
in
the
microsoft
space
wasn't
really
a
thing
back
then,
and
we
really
approached
like
everything
when
it
comes
to
tooling
and
everything
like
you
got
it
and
it
was
supported
by
microsoft,
where
today
might
like
even
we
at
microsoft,
build
tooling
based
on
open
source,
so
we
kind
of
use
the
same.
So
to
what
extent
like?
How
does
that
change?
B
C
I
think
you're
exactly
right,
like
a
lot
of
like
coming
up.
There
was
no,
I
mean
open
source
existed.
I
understand
that,
but
it
wasn't
in
the
microsoft
space
like
you're
saying,
and
there
was
what
nuget
was
sort
of
the
first
kind
of
like
I
can
get
these
packages
from
places
right.
That
was
new
because
it
used
to
be
like
you
get.
C
C
Yes
to
a
certain
point,
like
you
know,
so
it's
kind
of
that
balance
of
I
think
it's
just
the
world's
changing
and
looking
at
this
is
how
software's
developed
now-
and
this
is
how
we
go
about
it
and
we
get
tools
from
everybody
and
we
get
ideas
from
everybody.
I
think
it
you
know
just
sort
of
opens
the
world
up,
because
you
could
be
a
a
developer
in
a
country.
You
know
far
away
from
other
folks
and
still
have
a
huge
impact.
C
You
know
you
create
some
amazing
library
or
contribute
to
some
amazing
library.
I
think
that's
wonderful
to
see.
I
think
it's
a
way
to
kind
of
to
help
build
this
kind
of
global
community
of
people
developing,
and
you
know
just
because
I'm
not
sitting
in
this
or
that
city.
I
can
still
have
a
huge
contribution
to
something
right.
It
might
not
be
you
know
a
pnp
thing.
C
A
But
I
remember
in
those
meetings
at
some
points,
and
there
was
a
lot
of
discussions
on
okay,
so
we're
seeing
a
lot
of
usage
on
the
nuget
package,
we're
seeing
a
lot
of
uses
on
bmp,
powershell
and
growing
users,
and
then
there's
no
usage
for
bmpts
or
bmp
sites
and
test
core,
and
I
referenced
this
in
the
last
discussion
with
julie
as
well,
because
it
I
have
so
vivid
memories
on
that.
Why
isn't
anybody
using
this?
I
don't
want
to
I.
I
will
just
stop
doing
this
because
nobody
cares.
A
C
I
think
it's
just
a
consistency.
I
mean
I
don't
think,
there's
any
real
secrets,
I'm
terrible
at
promoting
things
I
mean
frankly,
like
I
really
am.
You
know
I've
if
I
was
better
I'd,
be
on
twitter
constantly
and
all
these
things
just
pumping
it
up,
and
I
I'm
bad
at
that-
I'm
not
good
at
that.
That's
not
what
I'm
skilled
at
and
I
think
it's
just
consistency
and
it
works
right
and
it
works
in
a
way
that
doesn't
have
a
lot
of
pain
like
it's
easy
to
get
going.
C
C
C
So
it's
just
blown
up
from
there,
which
is
fantastic
love
it
but
no
secrets.
I
I
really
couldn't
I
don't
know
if
I
could
do
it
again
like
replicate
it
again.
I
think
it
just
hit
at
a
time
when
people
like
a
lot
of
traditional
sharepoint
devs
were
transitioning
to
some
client-side
work
with
spfx
introduction
and
learning
typescript
javascript
some
of
that
world
and,
like
there
wasn't
anything
really
in
the
space
at
the
time,
and
we
were
there
and
so
that
started
to
get
some
pick
up.
C
I
think
it
helped
maybe
a
little
bit
we
did.
We
started
the
calls
I
used
to
every
thursday
host.
This
call
for
13
people
at
the
start
of
it
all
we're
up
to
a
few
hundred
now
but,
like
you
know,
it'd
be
a
few
folks
that
I
would
just
every
week
like
here's,
some
more
p
p
j
s
stuff.
You
know
this
is
what
I'm
going
to
talk
about
today
and
because
we
couldn't
talk
about
spfx.
Yet
for
the
first
you
know
four
or
five
months
of
those
calls,
because
it
wasn't
public.
C
A
D
A
A
Yeah,
I
I
guess
it's
the
combination.
Of
course,
the
consistency
communications
we've
been
still
communicating
quite
openly,
pmpjs
on
a
monthly
basis,
weekly
basis
and
promoting
that
it's
and
and,
of
course
the
community
course
for
sure.
Because
again
you
have
a
location
where
you
can
go
and
come,
and
then
there's
similar-minded
people
well.
E
B
I
guess
like
so
far
so
far
we
did
it.
We
didn't
mention
the
most
important
thing
or
one
of
the
most
important
things.
It
solves
a
problem.
People
have
exactly
right,
there's
a
clear
need.
Yes,
for
that,
like
you,
can
make
the
most
beautiful
and
communicated
thing,
but
if
people
don't
need
that
people
will
not
use
that,
whereas
here,
like
you
can
even
say
well,
I
mean
sure.
Maybe
there
is
room
for
improvement
to
communicate
it
and
get
out
there
and
show
what
it
can
do.
B
But
if
the
thing
itself,
if
it's
something
that
people
need-
and
it
solves
solves
problems
that
they
have,
they
will
go
the
extra
mile
to
figure
it
out
right,
even
if
the,
if
maybe
you
know
they
miss
this
one
sample
or
that
one
thing
is,
is
isn't
obvious
they
will.
They
will
do
that
because
they
will
see
that
hey
I
can
use
if
I
can
use
this
thing
for
four
out
of
five
things
that
I
need.
C
C
I
don't
know
weird
mostly
because
I'm
like
oh
okay,
cool
other
people,
know
about
this.
You
didn't
you're
talking
about
it
and
I
remember
the
first
time
I
saw
somebody
else
at
a
conference
talking
about
it,
which
is
just
like
well,
okay,
cool.
You
know
like
it's
fantastic.
I
love
it,
but
it's
just
so
weird
to
be
like
this
thing
we
started
is
now
like
just
a
thing
everybody
uses
and
talks
about
you're
like
okay,
that's
awesome,
fantastic.
B
C
Somebody
right,
you
know,
you
hear
him
say:
oh
man,
barbara
burr
and
you're
like
oh.
We
could
make
that
easier.
You
know
you
can
go
back
and
make
a
little
improvement
there,
or
something
and-
and
so
you
get
good
feedback
sort
of
passively
in
a
lot
of
those
forums
too
or
like
people
will
ask
the
demo
or
questions
and
you
could
just
sort
of
sit
there
and
listen
and
be
like
yeah.
That
could
be
easier.
You
know,
let's
go
see
what
we
could
do
about
that
and
then
sometimes
you
know
it
falls
into
that.
C
A
C
C
So
we
just
drop
the
old
one
and
just
use
the
new
one
and
stuff
like
that
a
little
bit,
but
mostly
it's
just
a
lot
of
boilerplate
removal.
I
don't
have
any
plans
for
v4
right
now.
I
always
coming
out
of
v2
knew
we
were
going
to
rewrite
the
guts
of
the
library
for
v3,
didn't
know
exactly
what
that
was
going
to
be
yet,
but
that
was
always
the
plan
right
now.
I
don't
really
have
a
plan.
Hopefully
julie
does
frankly.
C
No,
I
really
don't.
It's
only
been
a
couple
of
months
or
a
month,
so
it's
been
out
and
it's
other
than
a
few
things
right
at
the
beginning,
like
search
for
example,
that
we
just
beefed
it.
We
able
you
know,
it's
been
pretty
good.
Pretty
stable,
we've
had
a
few
little
other
things,
we've
missed
and
we're
getting
cleaned
up,
but
that's
been
good
and
then
v4.
B
C
I
don't
again
nowhere
like
I
don't
really
have
a
plan.
I
mean,
I
think,
if,
if
if
it
were
going
to
be
real
right
and
there
was
a
budget
around
it,
I
think
it'd
be
amazing
to
have
a
team
of
folks
a
couple
of
folks
who
could
help
with
issues
a
little
faster
iterate
on
features
a
little
bit
faster,
there's
stuff,
that's
like
in
the
issues
list
that
are,
you
know
like
enhancements
that
fantastic
would
love
to
do
it.
I
you
know
when
I've
got
time
right.
C
I
hope
you
this
week
fix
hack,
learn
have
a
little
bit
of
time,
maybe
to
get
in
there,
but
you
know
other
than
that.
I
think
it's
going
well.
You
know
like
nothing,
big,
truly
like
I
don't
right
now,
I'm
excited
to
see
what
the
community
does
with
the
new
kind
of
observer
pattern.
Thing
we've
come
up
with.
I
think,
there's
a
real
opportunity
for
folks
to
build
and
release
their
own.
What
we're
calling
behaviors
you
know
they
could
do
a
lot
of
neat
stuff.
C
We
had
an
idea
from
somebody
in
the
issues
list
that
we
ended
up
not
pursuing,
but
they
were
like.
You
should
support
indexeddb
right
as
a
place
to
stick
stuff
for
the
cash
and
we
looked.
We
looked
at
that
like
pretty
seriously
like.
Oh,
is
it
something
because
right
now
we
use
local
storage
and
session
storage
and
that's
easy
and
we
ultimately
chose
not
to
do
indexeddb,
because
it's
a
database,
it's
very
complicated.
Everyone's
gonna
have
opinions,
and
so
like
there's
no
like.
C
I
don't
want
to
be
responsible
to
like
re-expose
the
entire
api
for
indexeddb,
but
I
feel
like
that's.
If
you
want
to
build
that
it
wouldn't
be
terribly
challenging.
You
could
follow
the
patterns
we
have
for
our
the
stuff
for
caching
stuff
we're
doing
now
and
write
it
for
indexeddb
right.
The
way
you
want
it
to
work
because,
like
you,
gotta
allocate
your
stuff
and
your
indexes
and
all
the
stuff,
and
it's
like.
C
I
don't
know
that
I
should
do
that
for
you,
but
I
think
if
you
want
to
do
that,
for
you
I'd
love
to
see
how
you
do
it,
you
know-
and
I
think
it
was
a
really
good
idea,
but
not
everything
can
be
built
inside
the
library
because
sometimes
there's
too
many
options
and
how
do
you?
Because
any
choice
I
make
for
indexeddb
vasa-
is
going
to
have
a
different
opinion
in
waldeck
you're
going
to
have
another
opinion?
Oh
no,
it
should
be
like.
C
And
that's
great,
I
mean
that's
wonderful,
that's
how
software
should
work,
but
like
it
you
know,
I
think,
there's
a
real
opportunity
not
just
for,
like
that's
one
example
off
top
my
head,
but
I
think
there's
lots
of
other
things
victor
a
long
time
ago
said.
Oh,
you
should
base
your
whole
thing
on
axios
right
right.
Well,
no
we're
not
going
to
do
that,
but
we've,
I
think,
constructed
it
such
that.
If
you
would
like
to
base
the
entire
request
pipeline
on
axios
totally
doable.
C
I
guess
you
know
totally
doable
and
so
it's
it's
sort
of
balancing
that
what's
in
the
library
versus
what
we've
enabled
others
to
build,
was
a
big
theme
for
me
and
v3,
because
a
lot
of
stuff
people
would
ask
for
would
force
us
to
change
and,
like
I
said
there
are
these
clients
right
for
each
of
the
different
things
we
have
to
go
change
each
of
the
clients
right
to
support
that
new
feature.
That's
that's
a
bad
design!
That's
my
bad
design!
Right!
C
It's
all
on
me,
but
it's
like
that
was
one
of
our
big
things
like
we
got
to
be
able
to
open
this
up
right,
yeah
and
like
we
used
to
you
know
like
fetch,
you
pass
the
url
and
you
pass
that
init
object
and
we
used
to
like
have
our
own
init
object
and
we'd
get
the
stuff
on
it,
and
then
we
translate
it
over
to
the
other
init
object
and
all
these
things
right.
So,
if
somebody's
like
well,
I
want
to
use
the
property
that
fetch
supports,
that
you
guys
don't
support.
C
Okay
great,
so
we
have
to
go
add
that
property
300
places
whatever
new
model
we
just
expose
the
init
object
that
we're
ultimately
going
to
pass
to
fetch
and
you
do
whatever
you
want
with
it.
We
don't
care
like
put
put
everyone
in
there.
I
hope
it
works
and
we'll
throw
it
right
to
the
fetch
like
we
don't.
You
know,
do
any
translation
anymore
and
that's
again
where
we
got
a
lot
of
savings,
both
in
speed
and
just
overall
library,
size.
A
Yeah
discussion
point
which
I
know
we're
running
out
of
time,
but
we
are
kind
of
the
making
decisions
related
on
what
do
you
include?
What
are
you
not
to
include
on
the
library
rather
than
just
concentrating
and
expanding
and
expanding
expanding?
That's
not
necessarily
always
the
smartest
thing
to
do.
You
can
rather
branch
off
another
library
out
of
it
or
something
else.
C
C
This
was
this
what
we
call
selective
imports,
this
ability
to
like
just
bring
in
the
parts
of
the
library
you
need,
because,
like
tree
shaking
is
great
but
tree
shaking
doesn't
work
the
way
a
lot
of
people
think
it
works,
and
so,
if
you
reference,
you
know
a
whole
class
that
whole
class
gets
referenced
and
it's
going
to
get
included
right.
Even
if
you
don't
call
any
of
the
methods
and
so
our
old
architecture,
you
imagine,
you've,
got
webs
and
lists
and
items
to
do,
and
so
once
you've
included
webs.
C
You
basically
included
all
of
the
objects
in
sharepoint
right,
and
so
we
made
it
so
now
you
can
include
webs
and
lists
and
items
and
nothing
else
or
just
webs
and
lists
or
just
webs
and
and
that
was
a
big
thing.
So
that's
kind
of
a
little
bit
to
come
back
to
your
point
on
like
growth
like
making
the
library,
bigger
and
adding
functionality,
but
balancing
that
is,
like
the
selective
imports
kind
of
allows
that
to
happen
a
little
easier.
C
So
we
can
add
a
bunch
of
methods,
for
I
don't
know,
what's
off
top
of
my
head
taxonomy
right,
maybe,
and
we
could
add
those,
but
if
you
don't
need
them,
I
just
don't
import
them.
You're
good,
like
you
know,
and
then
we
also
have
talked
a
lot
in
the
past.
We
have
a
sample
about
it.
The
sort
of
preset
pattern
where
you
kind
of
create
one
file,
do
all
your
imports
there
and
that
way
you
don't
have
to
do
all
your
imports
across
every
file.
C
You
just
do
it
one
place
right
and
then
you,
it's
all
just
loaded
up
so
stuff
like
that,
has
been
really
good
to
try
and
balance
that
functionality
versus
size
versus,
what's
in
the
library
versus
not
but
definitely
encourage.
Folks,
if
you
have
ideas
for
stuff
to
be
in
the
library,
let
us
know
not
that
we'll
for
sure
include
it,
but
love
to
hear
those
ideas
and-
and
you
know,
certainly
if
we
don't
include
it
happy
to
help
you
produce
your
own
sort
of
add-on.
A
C
Using
this
library,
so
we
had
an
interesting,
I
remember
way
way
way
early
at
the
beginning,
we
have
a
function
in.
What's
now
called
the
core
library
pnp
at
pmp
core,
it's
date
ad
and
I
got
it
right
off
stack
overflow.
If
you
go
look
how
to
add
to
dates,
it's
the
it's
the
answer:
it's
got
the
billion
up
votes
or
whatever
on
stack
overflow,
and
I
took
it
and
credited
right
there
in
the
source
code
you
know
go.
C
C
Exactly
and
like
on
one
hand,
I
get
that,
but
on
the
other
hand,
it's
like,
and
maybe
it's
just
I'm
old
and
grew
up
where
you
just
write
our
own
code,
it's
totally
cool
like
you
could
just
write
that
and
we've
done
that
a
lot
of
places
where
I
you
know
I
need
a
little.
I
need
one
method
that
does
something
right
and
people
will
be
like.
Oh
just
why
don't
you
just
include
this
library
like
I
just
need.
I
just
need
this
one
function,
that's
three
lines
like
we
could
just
have
that
here.
E
A
C
Another
big
thing
that
helped
us
is
we
in
version
two
we're
still
supporting
ie
11,
which
means
you
have
no
access
to
modern
javascript
features
and
all
that
sort
of
stuff
and
with
the
new
stuff
we
are
basically
like
we're
typescript
four,
which
I
know
is
causing
a
little
bit
of
pain
and
friction
for
people
in
spf
x,
and
I
feel
that
pain
and
friction.
But
it's
the
right
decision.
C
B
C
Yeah,
so
we
were
able
to
drop
support
for
i11
and
and
we've
upped
a
lot
like
we've
made
more
assumptions
about
what's
available
like
in
javascript.
Like
you
know,
we
expect
this
or
that
function
to
be
there
like.
We
expect
reflect
to
be
there
now
we
expect
proxy
to
be
there
and
work.
Proxy
is
the
core
of
basically
everything
we
do
right
now,
and
so
it's
you
know,
it's
not
something
we
could
do
in
the
past
and
proxy
is
not
a
thing.
You
can
polyfill
right.
A
A
C
E
A
E
C
We're
excited
we're
excited,
so
if
you
have
feedback,
let
us
know
I'm
interested
in
the
feedback
like
I
said
we
can't
always
get
right
on
it,
but
we
do
our
best,
and
so
I
appreciate
everybody,
who's
used
it
over
the
years
and
helped
out
with
it
and
contributed
in
all
the
ways.
So
just
thank
you
and
thank
you
to
our
lovely
hosts,
visa
and
deck
for
having
me
here
today.
Thank
you.
Thank
you.
B
A
A
Of
course,
we
do
meet
with
patrick
multiple
times
in
a
week
anyway,
as
part
of
our
day-to-day
work,
but
but
still
really
good
to
catch
up,
and-
and
I
hear
your
thoughts
related
on
the
open
source
and
community
and
and
the
things
I
I
guess,
one
thing
which
seems
to
be
coming
up
in
many
of
the
discussions
always
related
on
the
successful
ones
and
and
the
things
which
are
having
attraction
is
consistency,
consistency,
consistency,
consistency
so
that
people
know
that
it's
a
thing
what
you
can
trust.
So
it's
not
just
now.
B
You
want
people
to
change
the
way
they
they
have
been
going
around.
That
thing,
whether
it's
like
imagine
you
ship,
an
sdk
and
they've,
been
calling
an
api
in
specific
way,
maybe
even
for
years,
and
now
you
ship
an
sdk,
and
you
want
to
use
the
sdk
instead.
Well,
that's
a
change,
it's
behavioral
change!
So
yes,
and
if
you've
been
building
an
sdk
for
six
months,
it's
top
of
your
mind
six
months,
and
maybe
you
even
thought
about
it
for
three
additional
months
or
maybe
more
so
it's
very
much.
B
It
just
makes
sense
for
you
right
like
there
is
like
you,
don't
need
to
explain
anything
to
yourself
anymore.
It
just
makes
sense
for
everybody
else,
it's
new.
Why
would
they
care
so
we
need
to
kind
of
you
know
rewind
and
go
all
the
way
back
to
all
the
different.
Basically,
the
same
thought
process
you
went
through,
you
need
to
take
everybody
along
with
you
right,
like
bring
them
along.
Hey
absolutely
so
we
have
this
thing.
This
is
the
problem
that
we
have
do
you.
B
Exactly
and
and
hey
like,
if,
if
you
want
there,
is
this
sdk
that
makes
it
easier,
better,
faster,
more
reliable
and
so
forth,
and
so
on,
yeah,
but
it
all
starts
with
like
it's
like
and
and
that's
the
thing.
I
guess
many
folks
underestimate
the
struggle
that
that
is
involved
with
changing,
behavior
and
thinking
around
things
or
others,
and
even
realizing
that,
like
it's,
it's
a
part
of
you
shipping,
a
product,
a
technical
thing
that
behavioral
change
is
also
a
part
of
the
release.
You
know
yes,.
A
And
which
is
a
super
critical
piece
or
should
be
a
super
critical
piece
of
the
release
so
that
you
actually
think
through?
How
are
you
addressing
that
change?
How
are
you
making
it
interesting
for
the
people
so
that
they
are
interested
on
even
looking
into
the
behavior?
Yes,
so
like?
Oh
that's
interesting,
maybe
I
should
have
a
look
on
that
seems
better
than
my
current,
whatever
I'm
doing
so
yeah
and
quite
often,
unfortunately,
we
we're
well,
everybody
is
busy.
A
B
It
is
exactly,
but
it
is
like
with
everything
else
like
you.
Imagine
that
you
type
on
keyboard
and
you
do
you
don't
time
blind.
I
guess
I
don't
know
if
that's
the
expression,
like
you
taught
yourself
to
type
over
the
course
of
years
and
you've
been
doing
that
for
10
20
30
years
now.
If
you
want
to
type
properly,
you
first
need
to
unlearn
the
habits
you
picked
up
along
the
way
and
that
is
slow
yep
that
is
painfully
slow.
B
So
you
need
first
to
acknowledge
hey
what
what
what
I
am
doing,
isn't
the
most
efficient
way
it
does
the
job.
But
it's
like.
There
are
better
ways
you
know
and
having
that
internal
drive
to
want
to
be
willing
to
improve,
I
can
throw
at
you,
you
know
the
best
keyboard
set
or
the
statistics
do
whatever,
if
you're
not
willing
to
change,
because
it
doesn't
click
for
you,
it's
irrelevant.
You
will
not
do
this,
even
if
it's
the
best,
even
if
you
would
type
like
you
know,
200
words
per
minute.
A
B
What
else
there
was
that
was
those
the
other
day.
By
coincidence,
I
watched
the
video
by
simon
sinek
yep,
and
it's
and
it's
it's
not
nothing
new
like
he
talked
about
it
a
few
years
back
already,
and
you
might
know
about
it
already.
You
know
the
circle
where
he
starts
with
the.
Why
and
then
the
how
and
then
the
what
you
know
so
like
like
really
starting
with
the
y
and
oftentimes.
We
don't
do
that,
like
we
always
like
hey
check
out
this
new
thing.
Here's
the
thing!
B
Yes,
it's
exactly,
it's
the
what
and
it
does
things
this
way,
so
it's
so
kind
of
work
backwards
and
feel
like
yeah,
but
why?
Why
would
I
care?
Why?
Why
why
and
we
kind
of
because
we
reverse-
that
we
start
with
the
wrong
kind
of
end
of
a
stick,
and
the
problem
with
that
is.
Is
that
apparently
the
way
the
brains
work?
Is
that,
like
there
are
three
parts
of
the
brain
and
decisions
are
made
by
the
to
like.
B
Why
and
how,
I
believe,
are
respond
to
emotion
which
are
really
what
drives
the
decisions,
whereas
the
what
is
just
you
know
the
facts:
the
features
the
metrics,
the
10x
20x.
This
feature
that
feature
you
can
do:
okay,
that's
cool,
but
like
you're,
not
deciding
on
facts,
you
decide
with
emotion.
Is
it
reliable?
Is
it
this
like?
Is
it
going
to
be
accepted
in
my
group?
Maybe
in
my
team,
do
I
want
to
change
everybody?
Will
people
think
that
I
am?
B
A
Know
so,
once
you
realize
that
it's
technology,
yeah
yeah,
especially
especially
we
don't
and
and
one
of
the
key
points
also
as
for
anybody
who's
building,
this
kind
of
open
source
projects
and
building
communities
is
to
understand
that
not
necessarily
the
person
who's
great.
On
writing.
The
code
will
be
great
on
actually
driving
that
behavioral
change
in
the
audience.
B
So
it's
the
same,
even
with
a
product
like
yeah
in
the
company,
you
have
a
person
that
goes
out
that
builds
the
product
that
invents
the
thing
that
builds
the
thing,
ships
the
thing
and
then
there's
maybe
someone
else
who
talks
about
it
right
and
the
bigger
it's
gonna
like
it
might
or
might
might
work
right
because,
like
you,
can
also
virgin
these
very
murky
waters
of
yeah.
But
you
will
get
this.
You
know
sleazy
salesman,
trying
to
pitch
me
something
they
don't
believe
in
yeah
yeah
I
mean
it's
very
much.
The.
A
Yeah
yeah,
so
it's
the
classical
thing
when
you
go
to
a
pre-sales,
consulting
whatever
gig,
and
then
it's
like
hey
so
check
out
this
cool
slide.
Or
are
you
actually
talking
about
stories?
I
kept
telling
the
yeah
how
it
how
the
person
who's,
considering
using
the
tool
or
buying
the
thing
yeah,
making
it
important
for
them.
B
It's
really
it's
the
same
thing
with
cars
clothing
like
look
at
how
much
attention
is
being
put
into
the
way
people
feel
like
you.
Will
you
you?
You
won't
see
an
ad
for
a
premium
car
about
yeah,
one
zero,
zero.
Two
hundred
that
many
horsepower?
No!
No!
It's
all
about
the
emotion
how
people
feel
you
know
the
sunset
or
sunrise
empty
road
freedom,
all
emotion,.
B
B
Yes,
imagine
you
know
you
have
like
somebody
like
sitting
out
there
on
patio
drinking
coffee
or
looking
at
something,
and
it
just
works
like
they
did
the
work
in
one
minute
and
it
just
works
and
like
they
don't
need
it's
exactly
that
and
they
have.
You
know
time
to
enjoy
family
and
do
other
things
they
want
to
do
right.
So
maybe
that
is
that.
A
Super
super
quick
yeah,
an
important
discussion
for
sure,
and
we
we
surprised
some
of
this
time
stuff
down
at
some
point
for
based
on
other
things,
but
today
we'll
do
the
articles
so
we'll
yes
get
back
on
the
normal
normal
agenda
of
the
show.
So
let's
actually
do
that.
That
was
a
that
sidetrack
right.
E
A
So,
let's
start
with
this
week's
articles
from
the
microsoft
teams
block,
so
there's
elevating
hybrid
experiences,
microsoft
teams,
rooms
and
teams
devices
and-
and
of
course
this
is
all
about
the
fact
that
there's
cool
looking
devices
now
that
we're
getting
back
to
work
and
back
to
offices.
But
some
of
us
are
some
so
we'll
be
working
remotely.
All
of
that
is
actually
taken
into
account.
So
some
of
the
tooling
some
of
the
teams
features
they
actually
promote
that
hybrid
experience,
so
some
of
the
people
will
be
in
rooms.
A
Some
of
the
people
will
be
working
remotely
and
they're
optimized
for
that
and,
of
course,
there's
new
devices
and
opportunities,
and
all
of
that
I
have
to
said
such
a
good
thing
about
this
logo
that
this
image
that
I
have
to
say
it's
actually
kind
of
funny
to
have
this
image
in
here
related
on
cozy
chair
all
of
that
stuff
with
a
touchscreen.
But
you
can
you
can't
touch
the
screen.
It's
maybe.
B
A
Really
cool
feature
for
sure
and
and
widely
requested,
or
there
has
been
a
lot
of
a
lot
of
bus
related
on
this
one
in
the
community.
For
sure
now,
on
the
sharepoint
block,
there
was
a
new
blog
post
from
mark
cashman,
around
village
md
designs,
a
legal
os
using
sharepoint
list
and
power
bi
being
a
technical
person.
The
os
is
always
like
operating
system.
Wait
what
what?
A
What
but
it's
kind
of
it's
operating
system
operating
system,
so
basically
they
they
have
a
storyline
with
the
customer
related
on
building
a
a
really
cool
setup
with
sharepoint
microsoft,
list
forms
and
power
automatic
and
power
bi.
So
using
the
tooling,
which
we
provide
as
part
of
microsoft,
365
and
then
building
and
adjusting
those
based
on
the
customer
needs
so
really
cool
story
line
for
sure
and
a
lot
of
a
lot
of
good
insights
on
this
story.
B
B
Managing
membership
of
communities
like
and-
and
I
think
they
build
a
power
virtual
agent
bot.
They
had
some
other
other
components
in
there
in
there
as
well
so
definitely
recommended
to
watch
this,
because
it's
a
cool
scenario
to
learn
about
and
who
knows,
maybe
it's
something
that
you
might
use
in
your
workplace
too.
Yep.
A
Absolutely
absolutely
and
there's
an
it
is
an
open
source
solution
as
well,
so
you
can
actually
access
that
information
and
code
directly
from
github,
which
is
really
really
cool.
Now
the
next
one
is
from
the
microsoft
365
pmp
block
from
lewis
afres
how
to
get
started,
deploying
azure
resources
using
fiset.
So
basically,
how
do
we
do
automation
in
the
usher
for
deployment
of
assets
whatever.
A
Yes,
that's
probably
oh
it
says
in
the
title
it
does.
It
has
important
resources,
but
basically,
how
do
I
define
that
reusable
definition
of
of
deploying
things
that
as
a
site,
have
to
automate
operations
and
then
use
the
cli,
and
how
do
I
use
the
tooling
on
that?
So
really
really
cool
thing
as
well?
How
does
this
relate
to
microsoft,
365?
Well,
of
course
the
code
which
is
connecting
to
the
tenant
is
running
in
azure
in
most
of
the
cases.
Technically
it
could
be
running
somewhere
else
as
well,
but.
E
B
If
you
build
a
bot,
an
api,
a
web
app
it
needs
to,
and
for
that
maybe
you
need
storage,
you
might
need
database
or
no
sql
or
cache
or
anything
else
you
might
need
on
azure.
You
need
to
roll
it
out
in
a
way
and
bicep
is
a
really
cool
way
or
a
language
I
could
say,
maybe
even
a
format
to
to
define
resources
that
you
need
and
to
roll
them
out
in
a
repeatable
way.
Yep
yep.
B
Templates,
so
they
are
like.
Basically,
the
purpose
is
they
do
the
same
thing
difference
is
between
how
readable
it
is
how
easy
it
is
to
write
and
so
forth
and
so
on,
and
maybe
in
a
way
preference.
Even
maybe
there
are
people
who
prefer
to
use
arm
templates.
There
are
folks,
maybe
who
use
the
biceps
style
description
right.
So
in
this
article
we
see
this
other
way
based
on
arm
templates,
how
you
can
assign
a
built-in
role
to
a
user
at
a
resource
group
right.
So
basically
you
have
something
on
azure.
A
A
So
how
do
I
actually
configure
the
permissions
and
scopes
in
a
way
that
the
application
hosted
in
azure
or
well
not
necessarily
hosted
in
azure
application,
which
uses
the
azure
id
to
get
in
will
only
get
access
on
a
specific
mailbox
rather
than
too
much
too
many
mailboxes,
because
by
default,
if
you
have
a
mission
set
the
mail
reader
mail
sent,
you
actually
are
requiring
that
that's
an
access
to
whole
tenant.
So.
B
Yeah,
so
if,
if
your
app
has
assigned
app
only
permission
with
these
two
scopes,
it
will
have
access
to
all
to
all
emails
right
so
because
that's
what
it
entails
right.
So
there
is
definitely
a
need
like
why
you
might
want
to
build
an
app,
but
have
that
app
not
be
able
to
access
anybody's
emails,
but
just
one
particular
email
box.
B
Exactly
one
color:
yes
exactly
so
in
this
sample,
he
shows
how
you
can
use
microsoft,
graph
toolkit,
which
is
the
easiest
way
to
connect
your
app
to
microsoft,
365
being
used
in
context
of
power,
apps
component
framework
and
how
you
build
custom
components
for
your
power
apps
that
are
based
on
microsoft,
graph
toolkit.
So
that
is
really
cool.
How
do
you
basically
use
the
power
of
mgt,
but
then
in
powerapps.
A
Then
we
had
a
update
from
julie
turner.
Last
week,
julie
has
been
working
with
stefan
bauer
on
the
h20
react
library,
so
basically
an
h2o
is
the
design.
Well,
it's
based
on
fluent
yes
fluent,
I'm
just
trying
to
figure
out,
I'm
always
confusing,
fluent
and
fluid
fluent
fluent
at
the
sign.
Language.
Hto
is
an
open
source
community,
styling
library,
for
it
so
based
on
css
rather
than
controls,
and
then
what
julie
has
done
based
on
the
work?
A
What
she's
been
doing
with
the
customers
is
that
she's
built
a
react
controls
on
top
of
those
designs.
So
it's
it's
kind
of
the
same
thing.
What
we
used
to
have
actually
at
some
point,
just
office
ui
fabric,
where
we
had
the
styling
and
css
separately
and
then
the
react
controls
on
top
of
that,
but
nowadays
that
doesn't
exist
from
a
microsoft
anywhere.
So
there's
an
h2o
which
is
providing
that
there
is
of
course,
fluent
different
set
of
fluent
controls
available,
but
there
are
always
controls
and
they
always
react.
A
So
it's
a
bit
of
a
different
alternative.
Why?
Why
do
we
need
to
have
this?
Why
is
it?
Why
aren't
we
using
or
provided
over
react,
north
star
or
other
components
matter
of
a
preference?
I
guess
so
exactly
it's.
It's
an
open
source
alternative
for
some
of
that
stuff,
and
it's
really
designed
for
sharepoint
framework
targeting
that
and
then
optimize
for
that
experience,
because
I
know
that
julie
has
been
implementing
a
lot
of
this
stuff
for
customers
as
well.
B
Crane,
yes,
then,
we
have
an
article
from
robert
crane
about
how
can
you
incentivize
people
who
are
active
on
microsoft
teams
and
how
you
can
do
it
with
power
automate?
So
the
idea
is
that,
as
people
become
more
like
imagine,
you're
a
lot
of
teams
in
your
org
and
you
want
to
you
want
to
become
a
thing
you
want
to
like.
B
So
you
want
to
basically
encourage
that
and
you
want
to
recognize
the
behavior
that
you
want
to
amplify,
and
here
robert
shows
a
solution
that
you
could
build
with
power
automate
to
keep
track
of
who's,
been
active
on
teams
and
recognize
these
people,
like
hey,
like
you're,
doing
awesome
job
you're,
helping
us
with
promoting
this
new
way
of
work.
This
change
again
that
we
want
to
embrace
right.
So
it's
a
cool
cool,
low
codes
approached
to
do
this
in
your
org.
A
Yep
makes
perfect
sense,
really
really
cool
stuff.
Also
from
the
recording
365.
Sarah
haas
had
a
blog
article
related
on
real
world
planner
use
cases
so
really
talking
about
the
different
options
where
the
planner
has
been
used
or
this.
To
be
honest,
this
is
a
podcast
or
is
the
video
blocking
like
we
are
together
with
myo,
yeah
and,
and
actually
that's
quite
an
interesting
discussion.
Point
also
is
that
do
we
use
do?
Are
you
using
planner?
Where
are
you
using
planner?
What
is
the
real
world
of
cases
using
planner?
A
B
A
B
A
A
Now
joanna
klein
had
a
blog
post
related
on
failure
to
launch
your
information
covenants
program
and
what
are
the
common
scenarios
and
why
things
are
failing,
so
so,
basically
understand
based
on
her
work
as
a
consultant
on
this
area.
What
are
the
common
mistakes
where
things
are
lacking
and
why
they
actually
fail?
So
really
really
good
thinking,
points
and
and
thoughts
thought-provoking
blockbuster
seriously.
Is
that
the
right
way
of
saying
that
that
sounds
good?
Yes,
of
course,
thank
you
john
on
that
one
and
then
our
good
friend
italian.
Here
we
go.
No.
B
How
do
you
go
about
approvals
in
microsoft
teams
right
so
in
microsoft
teams
you
we
have
this
ability
to
to
work
with
approvals,
requests
and
so
forth
and
so
on,
and
he
walks
us
through
what
it
is,
how
it
works
where
it
applies.
How
does
it
work
and
so
forth
and
so
on?
So
this
is
a
really
cool
way
to
learn
this
new
feature
or
feature
within
almost
eight
minutes
right
so.
A
A
Automate
powered
busy
lights
for
outlook
calendars,
so
basically
explaining
the
different
options
and
that
the
busy
lights
are
and
then
how
do
we
actually
modify
those
slides
and
how
do
we
integrate
to
power
automate
then
to
the
system
so
really
cool,
storyline
related
on
how
we
can
dynamically
then
controls,
for
example,
the
lighting
also
from
stream
deck,
so
would
that
finally
be
the
killer
up
to
my
stream
deck?
So
I
have
it
in
here,
but
I
don't
actually
use
that
often
so.
B
A
A
A
I
don't
have
a
specific
project
to
be
honest
with
this
week,
so
there's
a
lot
to
catch
up
on
and
to
do
so,
it's
easier
easier
to
focus
on
things
and
and
it's
always
the
challenge
of
prior
prioritizing
the
time
it
would
be
nice
actually
to
have
some
time
on
hacking,
but
there's
some
work
related,
attacking
which
I
would
love
to
do
as
well.
So
good.
B
B
Let
me
think,
let
me
think
again,
I
still
and
I
and
I
think
I've
been
repeating
that,
for
the
last
three
weeks
already
finalizing
the
work
around
a
poc
around
how
we
could
improve
the
developer
experience
for
angular
devs,
who
want
to
build
teams,
apps,
there's
just
like
one
or
two
things
that
we
need
to
figure
out
before.
We
have
something
that
we
can
show
to.
Basically
everybody
and
solicit
their
feedback.
B
That
is
one
two
we're
working
together
with
alex
and
I
guess
that's
again
something
that
I've
repeated
already
a
few
times
finalizing
the
work
on
that
having
kind
of
a
self-diagnosed
way
for
everybody
for
their
spfx
projects.
So
before,
if
you
have
an
issue
before
you
actually
submit
an
issue,
have
this
one
command?
You
can
run
as
a
check
just
to
verify
if
everything's,
okay,
because
it
will
be
a
waste
of
your
time
to
wait
and
everybody
else
is
like
oh
yeah,
but
you
have
two
references
in
there
and
you
only
need
one
right.
B
Exactly
here
is
the
way
to
fix
it
by
yourself
and,
and
maybe
that
will
already
immediately
fix
the
issue
you
have
right.
So
we
want
to
offer
that
ability-
and
basically,
at
that
point
here-
is
it
enough.
Are
there
other
things
that
we
could
check
for
to
make
it
easier
for
everybody?
So
I'm
working
on
that
finalizing
the
work
on
that
other
than
that
we
just
churn
as
we
go.