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
Yarn global not detecting license in package.json #3821
Comments
I tried to debug this, and it seems that what yarn is complaining about is not the license for package {
"dependencies": {
"create-react-app": "^1.3.1",
"typescript": "^2.3.2",
"xo": "^0.18.2"
}
} Those 3 are the only packages that I have installed globally in my system. As you can see, this file does not have a license, not even a name, so that's why a warning is thrown. Maybe the |
@bestander @arcanis I think this is the way to go. What do you think? |
* skip manifest validation when it's in global folder * Add tests
Thanks @olingern ! |
This is still happening though |
strange, i'm getting:
but in
|
@tony-kerz I was getting this warning when I had a |
@chrisdothtml that was totally it, thx man! |
I've the need to keep package.json in the root of my react-native app. How to turn off this warning in this case? |
@realtebo If you don't intend on publishing it as a package, you can just set |
Thanks, @chrisdothtml . I already did that, but nothing changes. |
When generating an app without client code, upgrade generator fails because yarn complains about no licence. Adding `"private": true` to `package.json` avoids this error and makes a lot of sense as there'sn o npm module to publish anyway. See yarnpkg/yarn#3821
@realtebo When u had a |
@iTonyYo : I am no more on the situation I reported some months ago, so I cannot try anything. But I like your reply and sticked the link into my personal dashboard, in the future I'll find it as first result before system will go on google to search. |
This issue has been closed but the problem has not been fixed. Why is yarn looking up the directory structure when it has already found the package.json file in the current directory? It's quite common for projects to exist inside other projects while in development state, especially using gitmodules. |
The problem described previously was that there was no package.json in the current directory iirc. You might want to open a new issue (with precise repro steps, please). |
@chrisdothtml Billal Begueradj |
This worked perfectly, i was messing around installing/re-installing node the other and forgot i didnt clean up after myself. |
just additional info, I have removed package.json and yarn.lock from parent directories too, directories were not projects, dont know how they appear there ))) |
I have faced same problem i.e How I overcome from this? |
... :( |
@iTonyYo Thanks, it works. |
I also have
Please HELP! |
Hi, did you just removed |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Installing global packages doesn't always detect license field.
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
For it to install without a warning about missing license.
Please mention your node.js, yarn and operating system version.
Node: v8.1.3
Yarn: 0.27.5
OS: macOS Sierra 10.12.3 (16D32)
The text was updated successfully, but these errors were encountered: