You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The package is MIT licensed, but the NPM package is missing a copy of the license. As such it is hard to satisfy MIT license conditions which require from me to include a copyright notice (which is otherwise found in the license file) as I am using the installed NPM package files and not the source code itself to search for the license file.
I think this should be as simple as adding LICENSE to the files list in package.json.
The text was updated successfully, but these errors were encountered:
Hey, no problem, we normally include the license file with our published packages, so this must have just been an oversight. I've added it to all three packages and have published new releases 👍
The package is MIT licensed, but the NPM package is missing a copy of the license. As such it is hard to satisfy MIT license conditions which require from me to include a copyright notice (which is otherwise found in the license file) as I am using the installed NPM package files and not the source code itself to search for the license file.
I think this should be as simple as adding
LICENSE
to thefiles
list inpackage.json
.The text was updated successfully, but these errors were encountered: