61–70 of 101 posts
With testing built into core, I’m looking forward to the reduction in complexity and number of external testing frameworks. I generally chose tape/ava in the past and vitest these days, but it’s awesome that now a very simple testing mechanism is available in core
Same. Every time I dive into a repo using Jest it infuriates me. So slow. The built in test runner is great.
What is the standard web application backend framework for Node.js these days, is it Koa? As I understand it express is quite dated because of the callback structure. I have been confused recently with the moving best practices. What is the server architecture Next.js is most often plugged into?
You can get pretty far with Next API routes as a replacement for a seperate Express backend. https://nextjs.org/docs/api-routes/introduction
Love this. I wonder if we'll eventually have a new merge à la io.js/node.js Deno and Node are converging more and more on every release, such a deja vu. The main difference being that deno offers much more as a business than just the "deno" product itself, so an eventual merge wouldn't be so trivial. Denode or Nodeno? Who wants to place bets?
I sure hope not. NodeJS is a FOSS project under the Linux foundation (via OpenJS) and is not driven by profit, while Deno is developed by a for-profit company (Deno Land Inc) which has bunch of closed sourced projects to fund the company. Hopefully, NodeJS learned from the whole Npm Inc history and tries to remain more independent from for-profit companies. The whole io.js thing was a very different thing than Deno.…
Earlier quoted context omitted.
You can get pretty far with Next API routes as a replacement for a seperate Express backend. https://nextjs.org/docs/api-routes/introduction
I’ve been using this and deploying straight to vercel (where they run as serverless functions.) Took some obscure googling to get things like sequelize to work, not overall it seems to work pretty great. However I would like to be able to control the resources (e.g. adding more cpu etc) and haven’t yet found a way to do so.
Earlier quoted context omitted.
> which is technically still in beta, but that just seems to be the maintainer being very conservative about a major release There hasn't been a new beta in a long time. Last release about a year ago and then the 1 before that about 3 years ago. Not a very convincing beta.
I'm not sure whether you mean "not very convincing" in the sense of "not reassuring that it works" or something else, but judging from users' comments on this issue about the release plans, it seems to work just fine: https://github.com/expressjs/express/issues/4920 The maintainer said this three months ago in a comment on that issue: > Express 5 is pretty much completed at this point, and we're just finishing up the…
Like how Windows XP on an old computer still "works just fine"?
What does work just fine in terms of software that's ever updating mean? It doesn't matter if it's called 4 or 5 or any other label.
On the comments: my point is more that we should not base the NodeJs standard on something that's not regularly maintained / updated. There are infinite amount of things that can be improved on for a "standard" server framework used by millions. You don't say Node "is done" and leave it? People would definitely fork it or move on (as happened in the past).
What is the standard web application backend framework for Node.js these days, is it Koa? As I understand it express is quite dated because of the callback structure. I have been confused recently with the moving best practices. What is the server architecture Next.js is most often plugged into?
They recently pushed their long awaited v5 update, which adds a Koa transport alongside the historic express transport, and improves the "code reuse between client & server" story for schemas/models/types.
Earlier quoted context omitted.
Why are you referring to it as that?
The big new feature is a sandboxing with explicit CLI flag opt in to permissions, exactly like deno pioneered. Except there's zero mention of deno as a clear inspiration of the feature.
Earlier quoted context omitted.
The big new feature is a sandboxing with explicit CLI flag opt in to permissions, exactly like deno pioneered. Except there's zero mention of deno as a clear inspiration of the feature.
Kind of reminds me of deno's support for package.json after realizing they needed the features.
They added the feature to "enabl[e] developers to transition from existing Node projects with ease."
Love this. I wonder if we'll eventually have a new merge à la io.js/node.js Deno and Node are converging more and more on every release, such a deja vu. The main difference being that deno offers much more as a business than just the "deno" product itself, so an eventual merge wouldn't be so trivial. Denode or Nodeno? Who wants to place bets?