Closed forivall closed 9 years ago
Solved by reinstalling the package. Issue filed in case anyone else had this issue when upgrading atom.
Hey, thanks a lot for reporting!
For future reference (mental note to self): There is a dependency that requires to be compiled on the system (pathwatcher). It is actually included in Atom, but unfortunately cannot be required by a package.
An official Atom-dev claims that dependencies are reused whenever possible, but that dependencies are still installed/compiled, so what seemed to happened here was that the already-built dependency didn't meet the minimum requirement of Atom/Node.
A reinstall might work because the dependency is compiled now matching the more recent version. It didn't work for me though, so I've updated the package (v0.1.2) so the offending dependency matches the "official" version used, it seems to do the trick.
Also updated the README to contain info how to install node with a matching version of Atom.
Yeah, I could tell that the recompile is exactly what happened and what solved it, I just neglected to explain that; thanks for explaining the backstory.
[Enter steps to reproduce below:]
Atom Version: 0.189.0 System: linux 3.18.10-1-MANJARO Thrown From: recent-files-fuzzy-finder package, v0.1.1
Stack Trace
Failed to activate the recent-files-fuzzy-finder package
Commands
Config
Installed Packages