So, firstly, the solid server is a prototype, and that includes the 4.x series and the 5.x series will also be prototypes, so this is all just prototypes in various stages of evolution.
There are various good reasons to run the beta, for one thing, you could be helping is drive the development forward, and you would not need to perform the migration steps that are needed from 4.x to 5.x down the road.
The 4.x series had an overly complex permissions system, which led to several flaws that had could have security implications, so there is really no option to stay there for long. 5.x doesn’t have that much practical deployment behind it, and therefore there might be issues that stems from the major change that we did in the permissions system, but it is basically a security issue that we had to address. Given that you shouldn’t stay with 4.x for long, and there is a bit of a jump from 4.x to 5.x, I’d recommend taking that leap now rather than later.
Personally, I would hope people would move along with the latest versions, as that is the most helpful in the long run, as I said, these are prototypes in stages of evolution, and the latest release is the latest stage of that evolution. Now, when we get to an actual non-prototype release, then the equation changes significantly, then remaining with an old version is an alternative, but as of now, semver regulates the version numbers and does not really reflect the maturity of the code.
That being said, it came as a surprise to me that npm would set the
latest tag to what is clearly semver-marked prerelease, it doesn’t seem to be a reasonable default to me. But since it did I wouldn’t be so inclined to change it either. So, I have to admit that was mostly a mistake, but since I hope people are willing to follow along, perhaps not a serious one.