Misha Kaletsky
@mmkal.com
Blueskposting about TypeScript & OSS: expect-type (~vitest), http://pgkit.dev, http://artifact.ci, trpc-cli, others Ex microsoft, http://zocdoc.com, http://havenhealthcare.rip, http://hidrb.com
Reminder that the National Popular Vote Interstate Compact exists and has a *chance* of coming into effect, it only needs a handful more purple states to sign on.
If you're frustrated to be voting in a non-swing state today, check it out and see how you can support it www.nationalpopularvote.com
If you're frustrated to be voting in a non-swing state today, check it out and see how you can support it www.nationalpopularvote.com
National Popular Vote
State status: AK AL AR AZ CA CO CT DC DE FL GA HI IA ID IL IN KS KY LA MA MD ME MI MN MO MS MT NC ND NE NH NJ NM NV NY OH OK OR PA RI SC SD TN TX UT VA VT WA WI WV WY The National Popular Vote bill wo...
www.nationalpopularvote.com
November 5, 2024 at 4:14 PM
Reminder that the National Popular Vote Interstate Compact exists and has a *chance* of coming into effect, it only needs a handful more purple states to sign on.
If you're frustrated to be voting in a non-swing state today, check it out and see how you can support it www.nationalpopularvote.com
If you're frustrated to be voting in a non-swing state today, check it out and see how you can support it www.nationalpopularvote.com
When vitest starts using the library you wrote as a prod dependency
November 4, 2024 at 3:52 AM
When vitest starts using the library you wrote as a prod dependency
I love this pattern. I'd go further than - not to be an defender of abstraction which is so uncool now - but in medium to large projects, you should usually do something like this for any dependencies that you use in more than a handful of places.
an underutilized pattern to add custom functionality to Zod:
create a "my-zod.ts" file that re-exports everything from zod. then define additional types/functionality in that file.
then you can do `import * as z from "./myzod"` to use your custom types alongside Zod's built-ins
create a "my-zod.ts" file that re-exports everything from zod. then define additional types/functionality in that file.
then you can do `import * as z from "./myzod"` to use your custom types alongside Zod's built-ins
November 4, 2024 at 1:57 AM
I love this pattern. I'd go further than - not to be an defender of abstraction which is so uncool now - but in medium to large projects, you should usually do something like this for any dependencies that you use in more than a handful of places.
Reposted by Misha Kaletsky
okay I made a starter pack with my favorite TypeScript folks from the old site, mostly OSS maintainers
let me know who I forgot 👀
go.bsky.app/84ChefN
let me know who I forgot 👀
go.bsky.app/84ChefN
OSS TypeScript Wizards
Join the conversation
go.bsky.app
November 3, 2024 at 12:01 AM
okay I made a starter pack with my favorite TypeScript folks from the old site, mostly OSS maintainers
let me know who I forgot 👀
go.bsky.app/84ChefN
let me know who I forgot 👀
go.bsky.app/84ChefN
Have we done tabs vs spaces here yet?
...tabs r bad
...tabs r bad
November 3, 2024 at 5:18 PM
Have we done tabs vs spaces here yet?
...tabs r bad
...tabs r bad
lol thanks @colinhacks.com for getting me to start using this!
Feels hopeful. Might see if I can start ignoring The Bad Place after Tuesday...
Feels hopeful. Might see if I can start ignoring The Bad Place after Tuesday...
November 3, 2024 at 2:06 AM
lol thanks @colinhacks.com for getting me to start using this!
Feels hopeful. Might see if I can start ignoring The Bad Place after Tuesday...
Feels hopeful. Might see if I can start ignoring The Bad Place after Tuesday...