Skip to content

add the license field in package.json.#20

Merged
kevinconway merged 1 commit intokevinconway:masterfrom
jinwoo:license
Jan 6, 2018
Merged

add the license field in package.json.#20
kevinconway merged 1 commit intokevinconway:masterfrom
jinwoo:license

Conversation

@jinwoo
Copy link
Copy Markdown
Contributor

@jinwoo jinwoo commented Jan 5, 2018

We are using an automated tool[1] for checking licenses in our packages
and their dependencies. The tool works best when packages specify their
licenses in the license field of the package.json files, as written
in https://docs.npmjs.com/files/package.json#license.

From the LICENSE file in the repo, I assume this package is using the
MIT license.

Hope you don't mind this change.

Thanks!

[1] https://www.npmjs.com/package/js-green-licenses

We are using an automated tool[1] for checking licenses in our packages
and their dependencies. The tool works best when packages specify their
licenses in the `license` field of the `package.json` files, as written
in https://docs.npmjs.com/files/package.json#license.

From the LICENSE file in the repo, I assume this package is using the
MIT license.

Hope you don't mind this change.

Thanks!

[1] https://www.npmjs.com/package/js-green-licenses
@kevinconway
Copy link
Copy Markdown
Owner

I don't mind the change at all and, in fact, appreciate that you'd be willing to put in a PR to resolve an issue.

This project is pretty well shelf stable and I haven't modified it in some time. It looks like jslint has changed significantly over time which is causing the build to appear failed despite this change only affecting the NPM metadata.

I've put up a second PR that adjusts the version pins to the last good values. This library has no direct dependencies except for those used to build and test so this shouldn't be impactful to anyone but me. However, I'd appreciate it if you could weigh in on whether or not this will affect your use of the library should I publish a new version to NPM: #21

@jinwoo
Copy link
Copy Markdown
Contributor Author

jinwoo commented Jan 5, 2018

Thank you for resolving the jslint issue! That doesn’t affect our use at all. Please go ahead and merge both PRs and publish a new npm. Thanks!

@kevinconway kevinconway merged commit 3cc6a5b into kevinconway:master Jan 6, 2018
@kevinconway
Copy link
Copy Markdown
Owner

OK. The CI/CD patch and the license annotation for NPM are now published as 4.2.1.

@kevinconway
Copy link
Copy Markdown
Owner

@jinwoo Due to some complications related to NPM, I've had to roll forward to 4.2.3. The 4.2.1 and 4.2.2 release were missing files and have been removed from NPM. I believe all of your projects are set to pull in the latest of the 4.X.X semver range so this shouldn't be an issue but I wanted to mention it just in case.

@jinwoo
Copy link
Copy Markdown
Contributor Author

jinwoo commented Jan 6, 2018

@kevinconway Thank you so much for your help! Yes, we can adjust the semver range accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants