This repository has been archived by the owner on Aug 14, 2022. It is now read-only.
Build failed at the [email protected] install script #542
Labels
Comments
IssueSame here, plugin stopped working: EnvironmentAtom
Operating System
Packages
Does anyone know an alternative plugin for this job? |
|
Thanks for the detailed reports. I haven't looked into this in any great detail yet, but it looks like you're both on arch-based distros. In the past, Atom via AUR has been patched to use the system version of Node, instead of the bundled (and often outdated) version of Node that comes with the official distribution of Atom. The error you're both getting looks to be caused by a breaking change in Node which breaks the Have you both installed Atom via AUR, and can either of you verify if it still patches in an unsupported version of Node? Thanks! |
|
@thomasjo Yes, i use an arch-based linux distribution. |
|
@thomasjo same here. Official Atom package from the Arch repo. |
|
There is no official Atom package for Arch/Manjaro. For pure Arch there is only a community maintained package, which is the one that @vivi90 is using. Official Atom packages only exists for Debian (.deb) and Fedora (.rpm). By official I mean available from the Atom community (e.g. https://atom.io). I had a look at the AUR package for both Atom and apm, and they are indeed using unsupported combinations of Node and npm. Using an official version of Atom (Fedora/.rpm), I get the following version information: The most important difference between my version output and both of your output is the Node version discrepancy. I'm quite confident this is the sole cause of your problem. As of right now this only affects those who use a packaged version of Atom that uses the "wrong" version of Node. In the future, once Atom updates to newer versions of Node, this will affect all users of this package. Unfortunately, abstract-socket is used by a dbus package dependency, which means that fixing your problem either means finding another dbus package that does not depend on abstract-socket, or remove dbus support entirely. The abstract-socket package hasn't been updated in a while (hence this build problem), and I'm not going to maintain a fork of the package. I'm tempted to remove dbus support entirely but that would mean removing support for many/most PDF viewers. TL; DR The problem is caused by atom package in AUR using a patched version of Electron, which in turn uses an unsupported version of Node. The abstract-socket dependency does not support this newer version of Node. Fixing the problem is non-trivial, and there is no clear path for how to proceed. Finally, I no longer use Atom, so investing a lot of my spare time towards fixing this problem, which only affects a minority of users is unlikely to happen anytime soon. I'm really sorry about that, but I've got other commitments and priorities. If either of you (or someone else) wants to submit a PR to fix this without breaking dbus support, I'm more than happy to merge the PR and publish a new version. Said fix would most likely involve finding a replacement for the dbus-native package that works with newer versions of Node (as well as 12.x). |
|
@thomasjo Okay so much input. What would be the easiest work around for now so i am able to compile latex inside atom again (without PDF viewer support is okay for me)? |
|
This issue has been marked as stale because due to inactivity. It will be closed in 14 days if no further activity occurs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm being unable to compile the Latex module. The problem is related to the npm abstract-socket package. Rebuilding that manually, however, didn't solve the problem
Error Code
Versions
The text was updated successfully, but these errors were encountered: