Maksim Sinik

I definitely agree with you, but not everyone agrees with us. 😔

Humans have the same error rate, though.

I fucking love the picture!!!!!

We should complete the migration in the next few weeks and put it in prod on a big internal monorepo. I will end up writing something for sure. I also have a name for the references/starter: “monorepo amara” XD

I discovered this feature by chance and went to update the readme. It is a killer feature for Nofe.js monorepos. If I find some spare time, I will create a reference repository to show the whole workflow.

AST based V8 code coverage is finally here! I thought of this feature first time over 2 years ago, but knew it would require so much work that I couldn't finish it by working on Vitest just on weekends. Ever since @stackblitz.com hired me to work on Vitest I knew I could finish features like this.

I reviewed this edition, and what was already a must-read book is now a mandatory read.
I highly recommend it to seasoned developers as well.

Cover of the book "Node.js Design Patterns, Fourth Edition" by Luciano Mammino and Mario Casciaro. The design features a dark background with a dynamic purple and blue wave pattern. At the top, there is a label saying "Expert Insight" and a hexagon badge that reads "Early Access." The subtitle reads: "Level up your Node.js skills and design production-grade applications using proven techniques." At the bottom, there are black-and-white photos of the authors and the publisher logo "<packt>".

📘 The new edition of Node.js Design Patterns is coming soon!

After 9 months of hard work with Mario Casciaro, we're finally ready to share what’s next for one of the most loved Node.js books.

But this is not “just another edition”...

Is it FE, BE or both? Depending on it, you have different options.

Again, there is a way to generate correct releases and change histories, but I get your point, and I share the struggle (but not the hate :))

You can point the npmjs link directly to the correct package in the monorepo, and that package is effectively what is published. The issue you are describing is misconfiguration on the repository field in the package.json 🤷‍♂️

I noted the same. But I am also sure this wasn't the case with the “dumber” models from 1-2 years ago.

Something very similar to 😎

Oh! I must remember this when you use that emoji next time.

RafaelGSS - Twitch Node.js Core Mentoring

Folks, right now @rafaelgss.dev is doing an awesome livestram on m.twitch.tv/rafaelgss talking about Node.js threads, memory management and perfs. Join us!

I updated fastify and its dependencies to 5.x.x in our private monorepo. Buttery smooth. If you need to do the same, follow fastify.io/docs/latest/..., and you’ll be covered!

This is a much-welcomed thing! Are there any docs already?

Node.js has had support for running TypeScript directly since v22.6.0. I’ve been wondering what a minimal Node.js with TypeScript starter project might look like.

Here’s my first shot at what I think might work for me. And it's my first blog post in over 2 years!

simonplend.com/blog/a-node-...

Ok, I got it. I’ll check it tomorrow. 👌

Awesome! What kind of help would be the most appreciated?

I think that the recommendation was more about not using top-level awaits, making the module async first. Yes, you are right: it works in *all* cases.

It definitely is. Just bump a major. It is a solid reason for bumping.

Yeah, I am subscribed, so it is literally a problem of “finding time.”

Uh, awesome. My sweet spot for game length is 20-25h at max. I might give it a shot!

How many hours does it last?

I thought the same, but I recently discovered the pleasure of learning new libraries using an LLM agent as a guide. It helps me learn by doing with a faster iteration loop. What do you think about it?

Lately, the only one that is not song it anymore is Crusor + 3.5
Everything else I tried does exactly what you two just said. Even if I explicitly say “do not change tests”, it does it after “thinking” and trying to convince me it is the correct thing to do.

Welcome to Italy! Enjoy your stay.

GitHub - ducktors/Valkeyrie: A Node.js key-value database A Node.js key-value database. Contribute to ducktors/Valkeyrie development by creating an account on GitHub.

Now that I have finished the base implementation for Valkeyrie, I will focus on the documentation. Until now, it has all been AI-generated with subpar results. Thanks to extensive tests and comments, I still want to figure out how to make it 100% AI-generated.

github.com/ducktors/Val...

There are no technical hurdles at this point. We're just building the solution now, hopefully in time for Node.js 18 EOL.