Closed Walt9Z closed 7 years ago
Which version of Hyperclick is this? This hasn't been an issue for quite a while now.
I'm seeing this issue as well. Version: 0.1.3
Error: Package not initialized
at Object.e.(anonymous function) [as observeTextEditor] (/home/parallels/.atom/packages/hyperclick/index.js:1:152957)
at Package.module.exports.Package.activateServices (/usr/share/atom/resources/app.asar/src/package.js:353:69)
at Package.module.exports.Package.activateNow (/usr/share/atom/resources/app.asar/src/package.js:187:16)
at /usr/share/atom/resources/app.asar/src/package.js:157:32
at Package.module.exports.Package.measure (/usr/share/atom/resources/app.asar/src/package.js:92:15)
at /usr/share/atom/resources/app.asar/src/package.js:150:26
at Package.module.exports.Package.activate (/usr/share/atom/resources/app.asar/src/package.js:147:34)
at PackageManager.module.exports.PackageManager.activatePackage (/usr/share/atom/resources/app.asar/src/package-manager.js:548:21)
at /usr/share/atom/resources/app.asar/node_modules/settings-view/lib/package-manager.js:439:29
at exit (/usr/share/atom/resources/app.asar/node_modules/settings-view/lib/package-manager.js:73:16)
at triggerExitCallback (/usr/share/atom/resources/app.asar/src/buffered-process.js:215:47)
at /usr/share/atom/resources/app.asar/src/buffered-process.js:229:18
at Socket.
@murali44 That's actually a different issue. Are you on the latest Atom version? The last report was using a very outdated version: https://github.com/facebooknuclide/hyperclick/issues/17
@hansonw Yup! upgrading to the latest version of atom fixed it. Thanks.
I saw same problem. My atom is 1.19.0. What I did is I deinstalled hyperlink and reinstalled it. It works now.
Same in here! After upgrading to Atom 1.19.
Same here. Atom 1.19.0 X 64.
In the past this issue has been solved by clearing the APM cache, uninstalling hyperclick, and then reinstalling it. Can you guys try this? https://github.com/facebooknuclide/hyperclick/issues/20#issuecomment-312954082
Same here on the atom portable version.
@hansonw I confirmed that that seemed to have fixed it for me. Thanks!
Just installed version 1.19.0...
Cannot read property 'getDomNode' of undefined
See attached Stack Trace