chartjs-plugin-stacked100 VS Nest

I understand what you feel. I lived an example with this contribution: https://github.com/y-takey/chartjs-plugin-stacked100/pull/48, where you can see the comment of "LeeLenaleee".So, yes it is hard, but on the other hand, just do it, and learn from people reactions ;-)

NestJS GitHub Repository

In this article, we will walk through a step-by-step process to secure a Nest.js RESTful API using Keycloak. This includes setting up an application client and configuring authentication and RBAC for your API endpoints.

The rapid evolution of web development in 2025 makes it imperative to choose a framework that truly fits your project. Whether this involves a dynamic web application, scalable API, or high-performance SaaS product, the decision to select Next.js or Nest.js becomes all the more key. While both do their thing really well, in this sense, they don't do the same thing.

nest.js

Ok, you're right.

I was referring to the usual ones (Next, Nuxt, SvelteKit, Remix, etc).

Joytick looks cool. Besides this there's also NestJS

https://nestjs.com/

Basic knowledge of NestJS and Javascript/Typescript.

https://nestjs.com - official framework website

In Action: A NestJS Example

But what ultimately made me disillusioned was encountering bugs and odd behavior over time. For instance, I have a directory called ./test/helpers which contains helper modules for my tests. This is a convention I learned from Nest tests during my time at Procore. Tap absolutely refused to ignore this directory (which had no tests in it), regardless of my efforts to configure it thusly.

We need to start with a base application, let's say a nestjs application, with vertical slice architecture, where our application is mainly composed by: controller, service and a repository.