Companies and individuals sometimes highlight their TypeScript usage as a point of pride. It's seen as an indication of high-quality code and rigorous standards.

Truth is, yes, it may impress your non-technical client when you tell them about how you have this extra step that's supposed to reduce bugs.

In reality, you've replaced the problem of clearly seeing the data types moving around your program with the burden of managing a TypeScript implementation, which is clunky and overly complicated. In reality, it often causes more problems (and headaches) than plain JavaScript. For example, spending an extra 1-2 hours just correcting type errors that don't matter.

Clean JavaScript is king 👑.

I just think is funny how people every year announce that some top javascript framework will die and nobody will use it

here the great example, they have been 8 years predicting the dead of Express.js, still the most popular server framework for javascrip

So what do you think guys, what is the latest framework or tool you heard it was announced as dead and which one you think it will really die?

I heard recently Angular.js, React Native and Redux...

but honesly redux it might die soon haha

The goal of this diagram is to show how I structure my SaaS app as a solo developer.

This is not “the perfect stack”, and I don’t think every project needs all of this. The goal isn’t to say everyone should use the exact same tools, I'm just sharing an architecture that currently works well for me.

At a high level:

Frontend: Next.js, React, Tailwind CSS, shadcn/ui, React Hook Form, TypeScript

Backend: Node.js, oRPC, Zod for the frontend/backend contract

Database: PostgreSQL with Drizzle ORM

Auth: Clerk

Payments: Stripe

Emails: React Email

Observability: Sentry + LogTape

CI/CD and quality: ESLint, Vitest, Playwright, Knip, Storybook, GitHub Actions

I turned this architecture into an open-source GitHub project here: SaaS Boilerplate

As a NodeJS developer who's a stranger to the DevOps world I've never really understood the hype around Docker.

In my quest for answers I read many articles explaining why containers are better than virtual machines, but I've rarely used a VM. Is Docker only beneficial for people who come from the VM world?

I wrote an article explaining the benefits of Docker using real-world scenarios that hit it home for me. No buzz words, clear language and with a spice of humor https://maximorlov.com/why-docker-whats-all-the-hype-about/

Now that Deno is supporting NPM, Do you think Node developers would migrate to Deno?

If Not why?

Inspiration: Node is Aging Like Milk

I recently posted an article about Node.js here, hoping to get some constructive feedback. Unfortunately, it seems my post wasn't well-received, and I ended up with a lot of negative karma and feedback.

Firstly, I want to sincerely apologize if my post came across the wrong way or if it didn't meet the community standards. My intention was never to spam or provide low-quality content. I genuinely wanted to learn and improve my writing and understanding of Node.js.

I understand that my article might have had issues, and I am eager to learn from them. If anyone is willing, I would greatly appreciate constructive criticism or suggestions on how I can improve my work. Your insights and expertise mean a lot to me, and I hope to use this experience to create better content in the future.

it was a p99 spike on one route and i went straight to adding timing logs everywhere like an idiot. ran the process with --cpu-prof, loaded the .cpuprofile into chrome devtools, and the flame graph showed 60% of the time in a JSON.parse of a config file we were re-reading per request instead of caching. no dependency, no apm agent, ships with node. i keep forgetting it exists until i've already wasted a day.

Node 16 is released with updated platform support and much more!

Node 16 has released on 20th April 2021 with updated platform support, V8 version 9, and more. This article studies the new features of Node 16 along with the deprecations and breaking changes.

Features and Updates:

1.1) Platform Support

1.2) V8 JavaScript Engine Version 9

1.3) Node-API Version 8

1.4) Stable Timers Promises API

1.5) Web Crypto API

1.6) Abort Controller

1.7) Buffer atob and btoa

1.8) npm v7

1.9) Async Local Storage APIs

1.10) Apple Silicon

1.11) Deprecations

https://www.geekstrick.com/news/node-16-is-released-with-updated-platform-support-and-much-more/

I scanned 250 public Node.js repos to study how bad blocking I/O really is.

Found 10,609 sync calls.
76% of repos had at least one, and some are sitting right in request handlers.

Benchmarks were rough:

• readFileSync → ~3.2× slower

• existsSync → ~1.7×

• pbkdf2Sync → multi‑second event‑loop stalls

• execSync → 10k req/s → 36

Full write‑up + data:
https://stackinsight.dev/blog/blocking-io-empirical-study/

Curious how others are catching this stuff before it hits prod.

I made a discord bot using node. You can use it to ban everyone on the server and gain admin perms on the server that its on. All you need to do is get the bot onto the server.

you can get the bot from here.

Features

• Ban everyone

• Get admin perms

• And more features to come!

Disclaimer

This bot is made for educational purposes only and im not responsible for what you do with it.

I'm creating a new ORM (no, I haven't lost my mind - there is a valid reason for my company to build a new one). I'm planning to open source it perhaps with a few premium features a la Prisma and would love the community's thoughts on what you'd like to see and use in an ORM. If you have 5 minutes, I've put together a quick survey. Thanks in advance!

https://5grrwlbqqzz.typeform.com/to/hOiHJuug

[DISCUSSION]

Lets have a discussion on why one is better than other.

Anyone experienced with both ?

Can anyone suggest some cool ideas for NPM packages? Need to publish a package for my final year project. Any kind of help is appreciated.

Thanks!