Unable to upgrade some packages #255
Comments
This seems similar to npm/npm#3559 |
It would be good to know if you can npm is currently being upgraded in #252 so it might be possible that this is already on the way to being fixed. |
|
What about |
That works fine, as well. |
And just to see, what version of |
|
Hmm, okay, I wonder if going 1.4 ➡️ 2.0 of npm will fix this. That is being done in #252 |
Hmmm, I'm not so sure. I set up a separate installation of npm 1.4.28, and I could still install
|
Can you verify it installs when referenced as a Something like:
|
It worked with
And it worked with
|
Could you try |
No dice. 😒
|
Thank you for your efforts in helping me with this (the 😒 up there wasn't directed at you). The issue persists (for the same five packages) after upgrading Atom to 0.174.0. Is there an ETA on when #252 will make it into a release? |
@jackmaney It should be in the next release, 0.175 |
Excellent. Once the release is made, I'll let you know if the issue persists. Thanks! |
I'm also getting errors when trying to upgrade the following packages:
For Color Picker, I get prettymuch the same stack trace as above (unable to get the
I can clone |
I've upgraded to Atom 0.175.0. Upgrading Color Picker worked just fine, but upgrades of the following packages failed:
Here is the (now shorter) stack trace that I get when trying to update Atom Lint:
The same
|
@jackmaney can you run |
Yes, they look correct:
|
For the heck of it, I tried uninstalling Atom Lint and doing a fresh reinstall of the package. No dice. |
Weird, I'm really not sure what else to try at this point besides opening the npm code from within apm on your machine and log out the environment when |
Hmmmm...apm uses its own special npm installation (as opposed to a global one), I take it? |
Yeah, apm bundles npm and spawns it with certain flags for building things against the node version that ships with atom |
Hmmm, okay, I'll try digging into the code later this week and see what I can come up with. Thank you for all of your help. |
Huh...using |
Same |
Actually...no. Good catch. For Markdown Preview Plus, here's the stack trace from the command line:
And here's the stack trace from within Atom itself (Settings > Updates):
No mention of |
On the command line, do you have any proxy environment variables set? like In Atom, if you open the dev tools, go to the console tab, and type |
For Linter Clang, here's the stack trace from the command line:
and from within Atom:
Unfortunately, I have to go for tonight, but I'll look into tacking some logging onto apm to maybe get a better handle on what's going on. |
Sorry, didn't see your reply above.
Yep, along with
Nope:
I was a bit confused about the |
The issue still persists in Atom 0.176.0. |
So just confirming one more thing, is your |
I added a fix over in #280, please let me know if it doesn't fix the issue after Atom 0.177 comes out, thanks |
Yes, the |
I upgraded to 0.177.0, and of the extensions above, everything updates except for Linter Clang and Markdown Preview Plus. The stack traces seem to be different enough for those two packages, that I'll investigate them separately (and, if necessary, create separate issues for those repos). Thank you so much for your help! |
Awesome, thanks for the update. |
This is a long-overdue follow-up from this issue, which is being brought up here by @kevinsawicki's request. Note that the current error messages are a bit different from the above linked issue.
I'm using OSX 10.9.5 with Atom 0.172.0.
I'm also behind a corporate proxy.
(Note that I'm routing https through http, as per this comment.)
I am able to view updatable packages in Atom via
Packages > Updates
. I am able to update all of my installed packages except for:Whenever I try to upgrade any of them, I get a stack trace isomorphic to the following (which is the stack trace from trying to update Atom Lint):
Things to note:
apm
on the command line./private/var/folders/kk/r0v_bq3x6bj58dyn_b3rb_wh0000gp/T/apm-install-dir-115014-3749-se8njm/npm-debug.log
doesn't exist in my file system.git clone https://github.com/Benvie/harmony-collections.git
goes through with no problems whatsoever. Likewise,sudo npm install harmony-collections -g
works just fine.At this point, I'm plum out of ideas. Any help would be greatly appreciated. Thank you for your time.
The text was updated successfully, but these errors were encountered: