-
Notifications
You must be signed in to change notification settings - Fork 64
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 packages without repository urls #2052
Comments
Yeah, this is a pain. Back story is that we used to deploy via Bintray and they required a source repo. But Maven Central doesn't have that requirement so we could remove the requirement. It'll just take some work to do that. Until then it isn't hard to manually deploy these repos. I've deployed this:
I'll keep this issue open as a reminder to remove the requirement. |
Makes sense, thanks for the explanation! It seems that there are some more libraries from the same 'set' that are needed. Thank you for your help, I really hope that we are on the finish line! :) |
Those have all been deployed and should be in Maven Central shortly. |
Apparently, I've skipped one of them :(. There is also |
No problem at all! That has been deployed:
|
Hello!
I have another dependency of
graphiql
that doesn't contain a repository url in its package configuration: https://www.npmjs.com/package/@motionone/dom. The version of@motionone/dom
that is needed by thegraphiql
version I'm currently trying to deploy is10.12.0
. It seems that here is their original repository: https://github.com/motiondivision/motionone/tree/main/packages/dom. The expected arifactId ismotionone__dom
.Do you think it would be possible to modify WebJars deployment mechanism so it could grab the files directly from NPM? If it's possible, I believe it would cover all of the possible cases and free you from these manual deployment requests. Honestly, I feel bad for bothering you already :), and I'm afraid that this may not be the last NPM package without a repo url that is present in this huge dependency graph. I encounter a lot of popular NPM packages without repository urls specified.
The text was updated successfully, but these errors were encountered: