gitpkg
gitpkg copied to clipboard
Publish packages as git tags
There should be an option to replace the already created tag with new changes instead of popping an error if same tag is requested.
[`package.json`'s `private` field](https://docs.npmjs.com/cli/v7/configuring-npm/package-json#private) can be used to denote packages that should not be published. It would be handy to use this field with gitpkg. For instance, given: ``` packages -...
Hundreds of people are using gitpkg, and the code is very seldomly changed. I think you can safely drop the `beta` and publish 1.0.0.
I'm trying to figure out how to be able to export a yarn workspace package in order to use within another internal project -- is this possible using gitpkg? Anyone...
It would be nice UX to add an install command with helpers for getting the latest `gitpkg` from a repo. Also, thanks for the really handy module. Very useful for...
npm 5 and yarn can't that can handle git tags with `@scope/name-package-1.0.0-gitpkg` notation (**last time tested**). That it's why I temporarily changed to a normalised version of scoped packages in...
Thanks! Just wanted to say that, since it helped me just now. :) Feel free to close this when you are done smiling. ;)
At the moment lerna doesn't link packages published as git deps (`lerna bootstrap`). I still need to try yarn workspaces.
> **idea/discussion:** just thinking aloud, comment whatever you think that could be wrong or could be improved. Long git tags are awful: ```json { "dependencies": { "some-package": "github:ramasilveyra/private-registry#some-package-v1.0.0-gitpkg" } }...
> **idea/discussion:** just thinking aloud, comment whatever you think that could be wrong or could be improved. Probably it will be possible to add the sha1 and sha512 on the...