Treora commented on issue #92: URL: https://github.com/apache/incubator-annotator/issues/92#issuecomment-695059327
I suppose we could continue using the `dev` tag that we once used? E.g. [`@annotator/dom`](https://www.npmjs.com/package/@annotator/dom) has a release `0.1.0-dev.9d100c0f`. As discussed in the last call, we could try set up a hook to automatically build and publish it on npm whenever the master branch has changed, while generating a version number from the commit number. On the other hand, I started wondering if we even want every development version to be pushed to the npm central registry. We discussed before that ideally people could just depend on the repository directly, using [a Git URL as dependency](https://docs.npmjs.com/files/package.json#git-urls-as-dependencies); e.g. writing `npm install https://github.com/apache/incubator-annotator#master`. The only problem we found was that our repo contains multiple packages. But perhaps we could still try make this work by making the top-level package the meta-package discussed in #90? If we want to publish pre-built packages, we could also create a branch (or branches, or a separate repo) that contains those, e.g. using [`publish-to-git`](https://github.com/Rush/publish-to-git/) to automate this. Or we can just publish the latest tarball on the website: e.g. `npm install https://annotator.apache.org/packages/dom/0.2.0-dev.tar.gz` would be nice? While it would be good to make our packages readily available in the npm *ecosystem*, this need not mean they have to be on the npm *central registry*. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
