Fetch default license from LICENSE about init-package-json HOT 5 CLOSED

I guess this is a nice-to-have kind of thing.

osi-licenses-full has the full license texts for several licenses. I guess this feature would go through each, calculate some "similarity" score with LICENSE and then just take a stab at defaulting on whatever license scored the highest?

from init-package-json.

licenses-utils does it by comparing files to static files stored as part of the module.
nlf does it by applying some regex.

Seems like either of these strategies would be fine.

from init-package-json.

The question I would have - where does this come into the hierarchy vs. config:init-license? Should the presence of a LICENSE always override the setting?

from init-package-json.

Should the presence of a LICENSE always override the setting?

That's the simplest and most intuitive thing to do. Explicit setting of the license in package.json trumps LICENSE, LICENSE trumps init.license, and init.license trumps the default (ISC).

from init-package-json.

I actually came here to create an issue for this. I tend to initialize a project with the respective LICENSE file on GitHub and run npm init -y afterwards. Would be great if it would detect the license automatically.

If this is something you would be up to have, I would be happy to look into creating a PR for this.

from init-package-json.