-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
install error #5327
Comments
There were some changes recently to the If it's an option for you, could you try with a more recent version of either of those tools? @dmarcos Could you push a tag for 21d017046216e318362c48abd1a48bddfb6e0733 to dmarcos/three-bmfont-text. I believe that should resolve the issue for anyone as well. |
error on npm 8.18.0
but yarn doesn't work |
Those warnings are to be expected as npm can't check integrity of git dependencies. It should have installed aframe and transitive dependencies at that point.
In what way 'doesn't it work'? Any error or warning message? Which version of yarn did you try? |
I can confirm the issue with yarn v1.x. Upgrading to newer yarn is quite a hassle. And it may not solve it as you said it appears to be a Git issue:
My assumption is that a regular clone does not retrieve orphaned commits. Github points out the commit was orphaned: dmarcos/three-bmfont-text@21d0170 Indeed pushing a tag for this commit would likely solve the issue. Ideally this dependency would be updated to a normal published npm package instead being pulled from github. |
Upgrading to a newer Yarn version shouldn't be such a hassle. It's the recommended thing to do when facing bugs or issues using v1.x and it just so happens that this isn't an issue on (at least) 3.6.0 🙂 It isn't really relevant what the default behaviour of a git clone is, as the package.json doesn't prescribe that. It just points to a specific commit in a repo which, as evident by the link you placed, can be resolved. Not sure since which version npm and yarn started resolving them, but it luckily means a workaround exists That's not to say that it shouldn't be addressed. A tag of the commit is the quickest and cleanest solution IMHO. While I do agree that it would be nice to only depend on published npm packages (and preferably also not custom forks), that wouldn't address the issue at hand (as already published aframe versions still reference the commit). |
Not sure what the problem is here. package.json points to dmarcos/three-bmfont-text@eed4878 which is the tip of master at the moment. dmarcos/three-bmfont-text@21d0170 should not be fetched. |
Maybe need to delete node_modules or reset yarn cache? not familiar with how yarn works. |
The latest release of aframe 1.4.2 still has a package.json that points to the dmarcos/three-bmfont-text@21d0170 Yarn v1/classic does a git clone + git checkout to install the package, which does not work because it's orphaned. So in order for people to install the release of aframe with yarn v1, you'd need to get the commit "unorphaned" by tagging it or make it a branch. |
I see. strange yarn behavior since the commit is still in the repo even if no branch references it. just pushed a branch pointing to the commit. |
closing this. can reopen if necessary. |
when installing by:
npm install aframe
or
yarn add aframe --verbose
The text was updated successfully, but these errors were encountered: