#TypeScript

83 tweets

#typescript 4.5 has been released and now it fails to compile code because of
TS2589: Type instantiation is excessively deep and possibly infinite.

Some combination of fp-ts, typebox is causing this now.

Replying to @coderbyheart

About the process: we are looking for people who love to make technology more
accessible, through great examples and documentation. That's why we try to
figure out your skills as a cloud engineer by checking for your #JavaScript and
#TypeScript skills in a coding challenge.

It's really annoying that @Azure is not keeping
their NPM release in sync somehow.

I cannot use @azure/arm-deviceprovisioningservices and @azure/arm-appservice at
the same time without #TypeScript complaining because they depend on different
versions of @azure/ms-rest-nodeauth.

It gets a little painful to keep CRA and #TypeScript working nicely together, so
I am really thinking about trying on of the new build-free tools like @pikapkg's
Snowpack or Vite.js...

HA!

I know use objects as arguments forever in #TypeScript to functions, because
this is always annoying:

const f1 = (arg1: string, arg2: boolean) => { // validate args, but must use
new name const _arg1 = v1(arg1); const _arg2 = v2(arg2); }

but this is cool: