Closed franzbertani closed 6 years ago
I'm having this same issue
Same here
For those who have this issue with atom v1.19.0, I fixed it by going back to 1.18.0
Same issue, too with Atom v.1.19.3
Investigating this, it seems the issue started on the release of 1.19.0beta0 - that's the earliest release I can find that suffers from it. I will investigate further. For now, it still works fine with 1.18.0.
I found a temporary fix for this,
The file lib/pusher/pusher.js
is not parseable alone.
Line 219 has }).call(this);
which is not closing any (function() {
https://github.com/pusher/atom-pair/blob/0607650e7a6b0965965ed144bcbfb92fbe5efae2/lib/pusher/pusher.js#L219
likewise, the line 3911 has a (function() {
which is never closed.
https://github.com/pusher/atom-pair/blob/0607650e7a6b0965965ed144bcbfb92fbe5efae2/lib/pusher/pusher.js#L3911
to 'fix' it comment out the line 219 and add this at the end of the file:
window.Pusher = Pusher;
}).call(this);
The window.Pusher
line is there to avoid another error later on.
My guess as to why this is happening is because this version of the Pusher js lib relied on the way the file was processed. I assume the previous versions wrapped the code in a function before evaluating it, which may be the reason the file was made unparseable alone in the first place.
Resolved, Atom-pair should now work for the latest version of Atom.
@kn100, would it be possible to add that to the release notes? I followed the link to https://atom.io/packages/atom-pair, then hit "Versions" to go to https://github.com/pusher/atom-pair/releases to see if this was resolved yet.
Good thought, I missed this. Thanks!
On Atom clean install
Atom: 1.19.0 x64 Electron: 1.6.9 OS: Mac OS X 10.12.6 Thrown From: atom-pair package 2.0.12
Stack Trace
Failed to activate the atom-pair package
Commands
Non-Core Packages