-
Notifications
You must be signed in to change notification settings - Fork 121
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
NPM/PIP - String does not have #dig method #449
Comments
Also getting the same with pip: Traceback (most recent call last): |
Duplicate of #448 could you share what dependencies you have (package.json, package-lock.json)? |
sure.
package-lock.json is too long to attach |
❤️ thanks for the assist @villelahdenvuo, and for the package.json for reproduction @timorkal ! I'll take a look at this (and #448) ASAP |
@timorkal there are two issues causing problems here. the problem with the npm source comes from an unexpected string value the problem in the pip source comes from an unexpected string value in the python property hash. Please see the docs for the expected configuration shape for the pip source. Note that there is a small typo in there - there should be a space between the key I'm addressing all of the above in #450 |
I'm still getting this error with 4.0.4 |
@rwwagner90 would you mind opening a new issue, including
|
I'm seeing this on |
Odd one is that running |
The error I see with CI is
|
@johnhunter 👋 we can fix the immediate bug but it will be released as a patch on the latest release series. As an FYI this tool stopped releasing executables with the 4.0.0 release, so you'll need to update your licensed usage and workflows to pick up the fix. would you mind opening a new issue and include package.json contents that reproduce the failure? this might be as simple as protecting against using the |
Thanks for the response @jonabc. |
Hello, I try to run basic cache command on a nodejs project and getting an error:
Using latest version: 3.4.3
licensed cache -c ./.licensed/licensed.yml
The text was updated successfully, but these errors were encountered: