-
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
Issue with yarn #20
Comments
(I raise this as it's causing our CI to fail: https://travis-ci.org/w3c/respec) |
This seems to be a growing pain with yarn. There are a few issues filed with yarn around fetching dependencies in git repos, this one seems to indicate that this form of the dependency name should work, and should also work with npm:
No plans to publish to npm for this repo. |
I totally respect that, but just wondering what your rationale is for not publishing to npm? |
It is an extra step beyond what I need to normally here, which is just tag the release. I do not expect a high amount of change for this repo, and I think its technology is falling out of favor. The installed name will not end up as just "domReady", as it needs to be namespaced in some way to fit into npm's global namespace. The github URL allows the "global namespace" to be unique, but to just use "domReady" as the local module ID dependency. So, mostly just feels like more of a hassle for the expected payoff for this repo, and some lingering annoyance at npm's global namespace affecting the local dependency name. I do appreciate that most other folks would not see these as big enough concerns to prevent npm publishing. |
@jrburke, really appreciate you taking the time to write up the justification. Makes sense! |
Not sure if this is directly related to domReady... but, given a package.json configuration:
Yarn install fails, because (I'm guessing here) it can't find the right package on NPM:
I'm wondering, could this library be published properly to NPM? I know npm and yarn can resolve github URLs, but it's nicer having things in NPM when looking things up.
The text was updated successfully, but these errors were encountered: