John Carew

Also, `VOGEN_NO_VALIDATION` disables it every object in the project. Which most of the time is no desirable, we need it disable only struct that are generated for EF core keys....

@ljharb this bug report is pointing out that the range does not work at all for pre-release.

I have tried all different types of formats. I just changed it to using a dash instead of period to test if it would work. And why are stating it...

Also this, doesn't seem to accept the range. ``` > npm install our-library@">4.2.32-beta.ge8343d1e" npm error code ETARGET npm error notarget No matching version found for our-library@>4.2.32-beta.ge8343d1e. npm error notarget In...

It installs with `^` but it does not find any later pre-releases upon running the `outdated` command. The pre-release is stuck as `Wanted`, and the newer pre-release is in `Latest`....

Should the value after the dot even come into play yet, as the patch number is already higher in the newer pre-release Example ```shell >npm install our-library@^4.2.29-beta.g8c00b605 npm warn deprecated...

That may be true and valid for public pre-releases, but for internal teams working off of shared libraries in repos, our patch versions increase with each build. The part after...

We are using patch version, as you can see that the patch version increments on each build `4.2.29-beta` -> `4.2.37-beta`

That is a difference of opinion. Pre-release build is just that, a release that is not stable, not one-off tests. They are versions of the code that can be used...

Ok, it is a npm opinion, but that should not force it upon everyone. npm is merely a package manager, it should not dictate a team's way of versioning when...