NestJS 12: ESM Packages, Standard Schema Validation and Native Observability
NestJS version 12 has been released, transitioning core packages to ESM and adding Standard Schema validation. It updates the CLI and introduces an observability SDK. Key changes include project generation choices between CJS and ESM, improved validation options, and lifecycle project hooks.
NestJS version 12 has been released, transitioning core packages to ESM and adding Standard Schema validation. It updates the CLI and introduces an observability SDK. Key changes include project generation choices between CJS and ESM, improved validation options, and lifecycle project hooks.
In context
- Topic: Datos y Analítica — Gobierno del dato, calidad, analítica y productos de datos.
- Source: InfoQ
- Published: 19/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
In data, the problem is almost never the tool. It is that two areas mean different things by customer and neither wants to give ground. You can install the most modern platform on the market and still have three sales figures in the same meeting.
My criterion is that data only helps if it arrives in time for the decision it is meant to support. A perfect report that lands on the eighth for a decision taken on the third is a useless report, however correct it is. Timeliness beats precision more often than people admit.
What usually goes wrong
The frequent mistake is starting with the tool instead of the question. The platform gets bought, everything gets connected, and only then does somebody sit down to think about what they wanted to know. It almost always turns out the important question needed data nobody was capturing.
What to watch
- Which concrete decision changes because of this and who makes it: without that, it is one more dashboard.
- Whether definitions are agreed across areas or each one brings its own to the meeting.
- Where the data comes from and what happens when the source system changes or fails.
How I read this entry
I would use it to review the full cycle, from where the data is captured to where somebody acts. The problem is almost never in the analytics but at the start: someone filling a field by hand, with no validation, in a hurry, not knowing what it is used for later.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
