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
I feel a little stupid to ask this question, but I have been reading the README of both npm-license-crawler and license-checker for a few minutes, and did not come to an exact conclusion which one is closer to what I need. From a project management perspective, I would like to be able to see the licenses of all components included in a production build. (EDIT: A colleague showed me how to do this with license-checker and some scripts he wrote.)
I would like to suggest to extend the first sentences of your README to clarify what exactly is the difference between the two projects.
I suspect the difference is in what "goes in" to the license analysis. I must admit that I am not an NPM / frontend developer expert, which is probably causing my issue.
The text was updated successfully, but these errors were encountered:
I feel a little stupid to ask this question, but I have been reading the README of both npm-license-crawler and license-checker for a few minutes, and did not come to an exact conclusion which one is closer to what I need. From a project management perspective, I would like to be able to see the licenses of all components included in a production build. (EDIT: A colleague showed me how to do this with license-checker and some scripts he wrote.)
I would like to suggest to extend the first sentences of your README to clarify what exactly is the difference between the two projects.
I suspect the difference is in what "goes in" to the license analysis. I must admit that I am not an NPM / frontend developer expert, which is probably causing my issue.
The text was updated successfully, but these errors were encountered: