Duplication in NPM's registry

[Irio]

Background

Recently, I was faced with a feature that could be solved by using datapackage-views-js. One of my first actions was to search for the package in NPM's registry.

Problems

https://www.npmjs.com/search?q=datapackage-views-js

Unfortunately, I felt confused because there were two packages with the same name. Also, the latest tagged version in Git – v1.2.0 – is not available in any of the published packages. I felt confused and wondering if the package was actually being maintained.

Expectation

I expected to see only one package available. I also expected to see v1.2.0 as the latest stable version available.

Proposal

The problems suggest that the publication of the package does not happen automatically, but manually by one of the developers. Travis CI configuration supports this hypothesis. Wouldn't that be a good opportunity to automate this task?

1. Delete one of the packages from NPM's registry.
2. Automate the task of publishing the package to NPM's registry.

cc @anuveyatsu

[anuveyatsu]

@Irio yes, we should publish to NPM automatically.

Example of how we've done it before - https://github.com/datopian/data-cli/blob/master/.travis.yml