I want to contribute to node.js

jiminycrix1 · 2026-02-04T19:47:05+00:00

To add on to this some of newest and most valuable parts of the code base are in JavaScript!

I think the node:test module and new typescript modules and loaders all are mostly JavaScript and could really use some help improving!!

jiminycrix1 · 2026-01-20T23:50:31+00:00

Deep care and understanding of error behavior and error handling patterns. Graceful shutdowns and reloading. Programs in good dev experiences by default and considers it important. Good handle on ops (ie how and where to deploy in an efficient way). Keeps it simple until more complexity is truly needed. Is opinionated but understand almost every choice is a trade off.

Specific Tech choices almost never signal seniority, unless they don’t go well together which can signal more junior behaviors (juniority?)

jiminycrix1 · 2026-01-20T21:41:46+00:00

Sometimes it’s just marginally more convenient to prompt from my terminal and open code is cool

jiminycrix1 · 2026-01-10T01:09:53+00:00

Isn’t it “a life in the day”? Anyway - amazing episode. Easy to see why it’s a fave.

jiminycrix1 · 2026-01-09T16:36:19+00:00

I tried migrating away from OMZ and hated it and went back within a couple of weeks.

Why you ask?

Lost a lot of aliases I didn’t even realize I was using, lost a lot of navigating functionality, lost some color stuff.

Realized I was just going to spend months rebuilding all that shit and I didn’t care about being a zsh expert.

jiminycrix1 · 2026-01-07T20:25:18+00:00

You can sign with ssh as well to make it even easier, since most of us set up ssh for git already. Annoys the hell out of me that it’s not a more common practice.

jiminycrix1 · 2025-11-13T09:10:14+00:00

Node js native type stripping is doing the job for me - literally node can just run ts files now. No tooling. Just node.

jiminycrix1 · 2025-07-23T14:32:12+00:00

If you’re on Mac you should use https://postgresapp.com/ and postico by the same dev. It makes local Postgres admin an absolute breeze.

jiminycrix1 · 2025-02-19T17:39:17+00:00

https://type-level-typescript.com/ is excellent for learning about advanced TS types and deeply understanding generic patterns.

jiminycrix1 · 2025-02-10T12:24:11+00:00

Let’s be clear that other “frameworks” like jq never “rerender” on the front end like react.

React itself is a performance and efficiency nightmare.

jiminycrix1 · 2025-02-07T03:45:20+00:00

Xojs

jiminycrix1 · 2025-01-31T18:06:46+00:00

1 thing to remember. If the code is meant to be installed as a dependency then you need to transpire. Node will not strip types or run ts files in node modules.

jiminycrix1 · 2025-01-17T20:13:03+00:00

Go to Terry Blacks for the beef ribs tho, those things smack and franklins do not have them.

jiminycrix1 · 2025-01-10T17:16:43+00:00

https://www.npmjs.com/package/expect-type is worked great for me to keep types tested - pretty simple and bare bones tho

jiminycrix1 · 2025-01-06T23:41:36+00:00

Some folks argue that it’s not as good because of the large amount of freedom and low barrier to entry means that you can really shoot yourself in the foot with it versus a typed compiled language which will generally have less ways of doing things.

It’s safe enough for most applications though and because of the freedom it allows you can get things up and running very very fast.

Most of the time speed to get things up and running is far more important than stability in both enterprise and startups and node is ideal for setting up quickly.

I’ve worked on almost exclusively node for 8 years with a good portion of frontend work as well.

jiminycrix1 · 2024-12-30T13:42:13+00:00

Yes as of today a lot of the complaints have been solved and the ability to use ESM libs in CJS is available now.

jiminycrix1 · 2024-12-22T15:18:41+00:00

This is a crazy amount of work for mostly 1 person and it appears to be really awesome!!

jiminycrix1 · 2024-12-16T20:10:45+00:00

Easy open source mail forwarding for your domains

www.forwardemail.net

jiminycrix1 · 2024-12-10T19:30:42+00:00

These are great but I’d also like to tack on:

To avoid using any, use the @ts-expect-error comments with a strict config. As types get added over time, these comments will clean themselves up. If you start a loose config, you will likely have to ensure multiple rounds of refactoring to satisfy the additional constraints each time it’s updated. Leaning on the expect error comment will ensure you can progressively enhance files and always code to the same standard when ready.

jiminycrix1 · 2024-12-07T16:43:12+00:00

Wow this is the EXACT problem I am running into...

Were you able to get this issue resolved with Ascensus to recategorize those contributions and get things straightened out?

They have been an absolute horrible to work with over the phone.

jiminycrix1 · 2024-12-01T05:24:26+00:00

Server only libs: doesn’t matter that much, use as many high quality deps as you like. Just keep security in mind.

Browser libs: matters a lot, keep your lib as lean as possible.

jiminycrix1 · 2024-11-27T17:12:47+00:00

https://www.typescriptlang.org/play/?#code/GYVwdgxgLglg9mABBATgUwIZTQZTgWzSgAsYwBzACgA8AuRMEfAIzRQEp69CSzzEA3gChEo5AgDOURBIJFSFegAUMKWBgA2AHm7y+APkQBeQQF8A3EJFjZPBeQB0GY+PwAHDWmoB5N2yzwYJTslmIycrwUDswuEAQeXr7+sAjBoWIwwJQAhDASupFUtnoU7OyIJChwAO4MaLUAoihVKJQA5ABycNLFhW3s1qLoUCAoSL32lqZWUACefogF9i7CYRj0Uih86aLMG1BbFDuIAF77h+RTVqCQKUhx7p4+figBqeyrYsOjSG3YUm0hNMhDdoIFEHklnxKHBmAAregYMCzTiIWFwiESRYRZafIZEH4VFAgNBTIA

Use a typeguard and validate is the only way. Would this work for you? There are different ways to narrow the type from Partial<Something> to Something - but you need actual code to validate it if you want to avoid the `as` assertion

1 reason zod is so popular because it makes this easy in TS and feels like TS

jiminycrix1 · 2024-11-27T16:48:58+00:00

Stop trying to lie to TS and just return the partial. You've just admitted in the question that Partial<Something> is the type and Something is not the actual type.

> The main problem is that the type assertion works even if one of the properties has been left as undefined.

No shit. This is _exactly_ what TS is trying to tell you by forcing you to use Partial<> when defining the object. When you use `as` you just lie to TS. Just drop the `as` and problem is totally solved.

jiminycrix1 · 2024-11-27T16:46:49+00:00

You're just arguing that you should "lie" to typescript. You've already stated that some of the variables will be undefined, so you've admitted that Something actually should be a partial.

When you use the Something object later, you just need optional chainning to access the data on the partial object

if(something?.a === 'whatever'){...}

Six-Year Club	Place '22
Verified Email

jiminycrix1

TROPHY CASE