-
Notifications
You must be signed in to change notification settings - Fork 35
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
--customPath not working as expected #103
Comments
license-checker-rseidelsohn --direct --customPath apps/proj-mobile/src/assets/config/customExample.json --json > apps/proj-mobile/src/assets/licenses/licenses.json Tried above it is not working with 4.2.9 and 4.2.10 either |
Hello @Prishii , thanks for your report. Actually, I am not able to reproduce your issue. Do you run it under Windows? |
Hello @atheck , I appreciate your bug report, but I can't reproduce it. Are you running it under Windows? Any more details would be great. Thanks a lot! |
@RSeidelsohn I'm experiencing the same issue which forced me to go back to 4.2.9 which works fine for me. I was able to reproduce it both on Linux and Windows. I've created a test app to illustrate the problem, here's my setup. package.json
packages_metadata_format.json
packages_metadata.json with 4.2.9 (output is following the format from --customPath as expected).
packages_metadata.json with 4.2.10 (output is obviously using the default format, --customPath flag doesn't seem to be working, also --direct seems to be ignored as well).
|
Just found this out myself, if you are requiring this package instead of using it from the command line make sure to use @RSeidelsohn The |
OK, I take it back, I wasn't paying attention. |
Oh I see, now it's working again as expected. Thank you @vladlen-g and @RSeidelsohn |
Hi, first of all thank you for your work!
Since version 4.2.10 I see an issue when using the --customPath option with a json file.
My format.json file looks like this:
But the output looks like this:
It is missing the required fields for
name
,version
,description
, ...With version 4.2.9 it works as expected.
The text was updated successfully, but these errors were encountered: