Closed lee-dohm closed 10 years ago
It seems to be an issue in node-runas package.
Interesting, I probably should have dug a little deeper :frowning:
@kevinsawicki helped me dig further after I got stuck in atom/apm#162. It appears that clang-flags
depends on an old version of pathwatcher
:
"dependencies": {
"pathwatcher": "^1.0",
"path": ">= 0.4.9"
},
@lee-dohm Thanks for the investigation.
@Kev Could you take a look and update the clang-flags
package?
Yes, I'll take a look at this.
any workaround?
atom-lint should install OK on 0.121 now. What is confusing me is that despite it installing, it then fails at runtime in the "Incompatible Packages" with
Atom Lint 0.14.5 Listed below are the incompatible native modules that this package depends on.
pathwatcher@1.5.0 Error message: Module did not self-register. runas@0.5.4 Error message: Module did not self-register.
It doesn't seem to be obviously easy to work out if this is clang-flags's fault or not.
pathwatcher should be upgraded to ^2.0.7
for Atom 0.121
I've asked for >=1.0 <3, which should be enough, shouldn't it? This covers 2.0.7 without breaking it for older Atoms.
Yeah, then I'm not sure why npm
is installing 1.5.0
then.
I don't think it is. Looking in
/Users/me/.atom/packages/atom-lint/node_modules/clang-flags/node_modules/pathwatcher/package.json
I get { "main": "./lib/main.js", "name": "pathwatcher", "description": "Watch files and directories for changes", "version": "2.0.7",
Which seems like the right version. It's a bit of a mystery to me where 1.5 is coming from
Can you try running the Incompatible Packages: Clear Cache
command from the command palette and reloading Atom?
I can, and I did, and now it doesn't think it's incompatible any more. OK, thanks. I think atom-lint is fine now.
I did an update and I got this:
(Tried Incompatible Packages: Clear Cache
didn't work)
Listed below are the incompatible native modules that this package depends on.
pathwatcher@1.5.0
Error message: Module did not self-register.
runas@0.5.4
Error message: Module did not self-register.
You'll need to remove atom-lint and reinstall it, then do Clear Cache. Atom only tracks available updates for top-level packages, not their dependencies.
So probably a new atom-lint is needed just to pull in this new dependency cleanly for users without them having to reinstall the package.
@Kev Should I specify "clang-flags": "^0.1.2"
in atom-lint
's package.json
? By the way, you seem to have forgotten to git push
to https://github.com/Kev/clang-flags.
I think if you keep 1.0.0 it'll still work on older Atoms, which won't have the new pathfinder? In any case, 0.1.2 is what's needed for the 0.121 Atom.
Thanks. I'll update the dependency to ^0.1.2
since the failure of installation is considered more critical than older Atom support.
Could have something to do with the update to Chrome 36 and Node 0.11.13 ...
Output: