How is nest.js versioned?

[novel sinew]

Hello Everyone,

I’m working on a large project to get things moving. I decided to use Nest.JS to implement our back bone services. The first month of Nest.JS is awesome! It guides me towards a productive workflow and is flexible enough to keep up with our demanding quality standards.

I read some random articles claiming that next.js has problems / issues with versioning (Every great framework, library, language, person, company had problems at some point right..)? Does someone have experience with random features breaking when Nest.js released a minor update or a patch?

Does Nest.JS have any practices on how to implement framework agnostic code? Currently I use providers to implement my framework agnostic code. To validate the workings I make sure to write tests..

[hasty sand]

with random features breaking when Nest.js released a minor update or a patch?

Nope. In fact, I'd venture to say, Nest's quality is top-notch in this respect.

That being said, this should not be a get-out-of-jail free card. If you do any upgrading, it should have testing behind it in an environment other than production.

Does Nest.JS have any practices on how to implement framework agnostic code?

Nope. You follow whatever best practices you want to follow. Providers is a way and it is Nest's way. In fact I have to ask while thinking about it, when you say "framework agnostic", what does that mean?