Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License URL issues in submodule packages #32

Open
bnash2501 opened this issue Apr 26, 2019 · 4 comments
Open

License URL issues in submodule packages #32

bnash2501 opened this issue Apr 26, 2019 · 4 comments

Comments

@bnash2501
Copy link

We've recently started using npm-license-crawler to generate our dependency list so our React Native app can have a license list that can link to the license files directly.

There are two issues with the generated license URLs that we have found in regards to submodules, in some cases.

For example, AppCenter-SDK-React-Native has several child packages that we use. The main repository uses LICENSE while the submodules use LICENSE.MD. Would it be possible for submodules to refer to the actual submodule license file instead of using the parent url? Or even possibly, check that the URL to the generated license file is even valid?

I've additionally opened an issue with AppCenter Issues to fix their file extension mismatches, but was hoping this was an edge case that could also be accounted for here as well.

@mwittig
Copy link
Owner

mwittig commented Apr 27, 2019

Hi, Thanks for using npm-license-crawler and your report. I'll will look into this asap.

@bnash2501
Copy link
Author

Thanks so much!

@mwittig
Copy link
Owner

mwittig commented May 6, 2019

Hi. I have briefly investigated the case. Generally, if a sub-module uses a LICENSE.MD file this discovered and the license URL is output accordingly. However, in the example "AppCenter-SDK-React-Native" the problem is that the submodule package.json contains the "repository.url" property of the top-level repository. As the URL is constructed using the Repository URL plus the filename this leads to a wrong URL path in the given case. Even though it is a edge case in my opinion I would like to find a solution for it.

@bnash2501
Copy link
Author

Cool, thanks for spending time looking into it. AppCenter maintainers have said they will be fixing the name mismatches.

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

No branches or pull requests

2 participants