atom-ink: Failed to activate the ink package
Error report
- Open ATOM
Atom: 1.14.3 x64 Electron: 1.3.13 OS: Unknown Windows version Thrown From: ink package 0.6.3
Stack Trace
Failed to activate the ink package
At Cannot read property 'text' of undefined
TypeError: Cannot read property 'text' of undefined
at render (/packages/ink/node_modules/etch/lib/render.js:6:18)
at addChildren (/packages/ink/node_modules/etch/lib/render.js:39:24)
at render (/packages/ink/node_modules/etch/lib/render.js:29:21)
at Object.initialize (/packages/ink/node_modules/etch/lib/component-helpers.js:40:23)
at Toolbar.Etch (/packages/ink/lib/util/etch.js:17:10)
at /packages/ink/lib/util/etch.js:108:21)
at render (/packages/ink/node_modules/etch/lib/render.js:17:25)
at addChildren (/packages/ink/node_modules/etch/lib/render.js:39:24)
at render (/packages/ink/node_modules/etch/lib/render.js:29:21)
at Object.initialize (/packages/ink/node_modules/etch/lib/component-helpers.js:40:23)
at /packages/ink/lib/plots/pane.js:24:10)
at Function.fromId (/packages/ink/lib/util/pane-item.js:74:36)
at Function.activate (/packages/ink/lib/plots/pane.js:14:28)
at Object.activate (/packages/ink/lib/ink.coffee:23:9)
at Package.module.exports.Package.activateNow (/app.asar/src/package.js:218:19)
at /app.asar/src/package.js:190:32
at Package.module.exports.Package.measure (/app.asar/src/package.js:96:15)
at /app.asar/src/package.js:183:26
at Package.module.exports.Package.activate (/app.asar/src/package.js:180:34)
at PackageManager.module.exports.PackageManager.activatePackage (/app.asar/src/package-manager.js:550:34)
at /app.asar/src/package-manager.js:531:29
at Config.module.exports.Config.transactAsync (/app.asar/src/config.js:337:18)
at PackageManager.module.exports.PackageManager.activatePackages (/app.asar/src/package-manager.js:526:19)
at PackageManager.module.exports.PackageManager.activate (/app.asar/src/package-manager.js:508:46)
at /app.asar/src/atom-environment.js:814:28
Commands
Non-Core Packages
git-plus 7.3.3
ink 0.6.3
julia-client 0.5.12
language-julia 0.10.0
latex-completions 0.3.2
tool-bar 1.0.1
uber-juno 0.1.1
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 7
- Comments: 28 (11 by maintainers)
Failed to activate the ink package Cannot read property ‘on’ of undefined Show Stack Trace The error was thrown from the ink package. This issue has already been reported. View Issue
The new version of Ink can’t be activated properly. I can’t use the rich console anymore.
Could anyone help me out, please? Thank you!!
[Enter steps to reproduce:]
Atom: 1.23.3 x64 Electron: 1.6.15 OS: Mac OS X 10.11.6 Thrown From: ink package 0.8.1
Stack Trace
Failed to activate the ink package
Commands
Non-Core Packages
I uninstalled uber-juno, juno-client as well as ink. I then closed Atom, re-opened and reinstalled all of the aforementioned packages. I get the following error on Ink…
Atom: 1.25.0 x64 Electron: 1.7.11 OS: Microsoft Windows 10 Home Thrown From: ink package 0.8.3
Stack Trace
Failed to activate the ink package
Commands
Non-Core Packages
I have a similar issue here after upgrading my Atom to latest version and reinstalling ink and julia-client. I think it is a similar issue as what previous guy also pointed out, but under a different environment. My environment is Windows 10. Can anyone help out? Thank you!
Atom: 1.25.0 x64 OS: Windows 10 Thrown From: ink package 0.8.1
Stack Trace
Failed to activate the ink package
Non-core Packages
@bbbales2 That fix is correct. 😃 The actual bug on our side was not having a upper limit on etch’s version, which I’ve fixed with https://github.com/JunoLab/atom-ink/commit/42587876e7ee948121f3aa1ccd851038354c3acf. Would be awesome if someone (meaning @MikeInnes 😉) could cut a new patch release (can’t do that myself on this machine for some reason)!
Probly not the greatest fix in the world, but it looks like there’s some sorta clash with this etch library thing (looks like etch got updated recently https://github.com/atom/etch/commits/master)
I had the same issue. After installing stuff, I was able to downgrade the copy of etch inside ink to make everything work.
On my computer that was something like:
cd ~/.atom/packages/ink/ npm install etch@0.8.0
I don’t really understand this atom/npm stuff very well so this might be a bad idea. Anyway look at the logs to see where this folder is located on your computer and maybe this’ll work for you.
I have the same issue