Publish to NPM with proper LICENSE metadata.

[alexkrauss]

The newest version of this package on NPM still specifies "license: none" (https://www.npmjs.com/package/base64id).

Can you publish a new version to NPM which has the proper license tag in package.json (This is already there as of commit 51bc378, but it is not published yet).

Having proper license metadata helps managing large projects with complex dependencies.

[VyvIT]

+1

[tmpvar]

bump

[shinichy]

+1

[danielstreit]

+1

[cheesymoo]

+1

[KristianSelnas]

Please note that the format added in 51bc378 is not valid (deprecated) according to the official npm documentation, see https://docs.npmjs.com/files/package.json#license

[kapouer]

Please note that the LICENSE file is absent from the published module on npmjs.org.
While the wrong/missing key in package.json isn't really a legal issue, the fact the license is missing from the files when installing through npm install base64id can be problematic.

[edi9999]

Please add this to npm !

[Samsy]

Could this be fixed please ??

There's 2,634,699 downloads in the last month on NPM, and the licence is still not fixed..

[rogierschouten]

Please see #8 The package.json uses deprecated constructs

[darrachequesne]

Released as 1.0.0.

[edi9999]

Thanks !