3 ms·
The thing I don't get, is, I'm using Git repos as source for my packages for years now, why can't everyone do this?
by k__ 7y ago
The thing I don't get, is, I'm using Git repos as source for my packages for years now, why can't everyone do this?
- threeseed 7y agoNot everyone tags releases so you're stuck if you need a fixed version of a dependency. Or you can tie it to Github and then download a release from their CDN.
- Kovah 7y agoYou can indeed reference a git repository with a single commit specified, like described in the npm install docs[1]. Not very user friendly, but it works. Example: "dependencies": { "myprivatemodule": "git+ssh://git@github.com:user/project.git#commit-hash" } [1] https://docs.npm.red/cli/install.html https://docs.npm.red/cli/install.html
- k__ 7y agoThis! plus treating every commit as major version and be done with it.
- Cthulhu_ 7y agoThat's a bit too idealistic; in practice, any commit MAY have a bug which passed quality control. The problem is that it's all down to people's discipline, it's not an enforced standard. A package manager where every release has to be reviewed, tested and approved before they become generally available would be a pretty interesting case, I know bigger companies who are reluctant to upgrade because of known bugs in the past would be willing to pay for something like that.
- timw4mail 7y agoI'm pretty sure you can use a commit hash as a version, too.
- roryrjb 7y agoI have only done this partially over the years, but yes I agree, it's a viable alternative and when it comes to private internal modules you don't ever have to worry about singing up to npm enterprise or deploy Nexus or equivalent.
- leshow 7y agoBecause versioning & dependencies are a nightmare that way
- borntyping 7y agoBecause package managers are used for more than just source code - many packages want or need to distribute intermediate or compiled artifacts.