-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Licensing issues with dependencies #5640
Comments
@selfagency Hi, good catch. These are forks of packages from https://github.com/graphql/graphiql that we haven't updated in a while, and the upstream didn't have licenses on them until graphql/graphiql#849 Will look into publishing versions with MIT license, but to check — are you sure that these are actually dependencies of Apollo Server? I don't actually think Apollo Server 3 depends on these, even transitively. Can you share a package-lock.json that shows that these were pulled in? I think they are used by the |
(apollographql/apollo-tooling#1553 and apollographql/apollo-tooling#2089 are relevant to the CLI here. Going to figure out why @hwillson closed the latter recently. That said, the main fix here is killing off the |
Yeah, |
It appears it's |
Aaaaand finally, |
Anyhow, thanks for your help. |
Thanks. Yeah, it looks like |
Looks like it hasn't been updated for over a year (15 mos). Ouch. |
Appears other Nuxt users have noticed as well. |
The following dependencies of Apollo Server/Apollo Client are throwing errors in my licensing compliance tools because they do not contain LICENSE files. Could you please add the appropriate licenses? Thank you.
The text was updated successfully, but these errors were encountered: