3 ms·

Re: dependencies, for "low-upkeep" projects I also like pinning specific patch numbers instead of doing any kind of semver pattern Also +1 to using files as a

Re: dependencies, for "low-upkeep" projects I also like pinning specific patch numbers instead of doing any kind of semver pattern Also +1 to using files as a DB for small-scale projects. Something I've done a few times is keep a single in-memory JS object as the source of truth, and just write it to disk as JSON on a certain cadence/read it from disk at startup. It's wonderful having your little one-off server not need to be a distributed system from day 1.

y4mi 5y ago
SemVer was specifically for libraries. It's really pointless to adhere to it if your code won't be imported into software projects of other people.
- brundolf 5y ago
  I meant for my dependencies, so they don't automatically change underneath me, even in ways that are harmless according to semver
  - y4mi 5y ago
    My only point was that SemVer is unnecessary if you're the only consumer of that code. A simple integer or a date would work just as well and would be much easier to automate.
    - brundolf 5y ago
      Maybe, but that's not at all the situation I'm talking about