Nickolay Kulikov

Well, I've solved my problem by just calculated it's sha256 digest using "crypto" and writing the result into the log. But initially I tried to use "morgan" together with the...

It feels like a dead end here... **May I ask for a couple of more independent reviews from third parties which are not affiliated by no means with the previous...

Ok, then if you do so, how long are you going to be on 0.x.y version. Does "0." mean something for you? And if yes then what?

So, you're saying 0.x are production ready? Then it should be explicitly stated in the docs I think (specifications of npm). Now it seems kinda opposite.

and if I want to publish something not production ready, but for people to try, how should I describe it in versions then (if not 0)?

And when I'm done I just drop "beta" and stay with 0.x.y. Ok, fine..but what's the point for me to start from 0.x.y ? I'd not be able to convey...

Ok, let's say I use pre-release (aka alfa, beta) to mark my versions as not production ready, as we agreed. 1.0.0-alfa< 1.1.0-alfa

And so, do you agree that an initial development process involves much more breaking changes than, let's say, when a package in production use already? Not least because we don't...

> and no, it'd be totally fine to publish a v1.0.0 after you had a v123.0.0-beta. I've looked it up v1.0.0 < v123.0.0-beta , according to semver and two very...

I'm on node:16-alpine and this is seems like an issue still. I set --remote-debugging-port=9222 and it magically works for me (what I don't like 😀) without even installing dbus. (I...