This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17.4k
Potential conflict between new frameworks and packages extending atom-ide #25398
Comments
A copy of the link above, for posterityI'm on Arch Linux, latest updates as time of posting. running Atom v1.61.0-beta0. I'm encountering the same issue across three installed packages: stack trace:
stack trace
stack trace
My ConclusionI ran into a few walls attempting to debug this because i'm not exactly a pro. I think this problem is an issue with atom and not the packages themselves. |
5 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
0 participants
OS: Arch Linux
Version: v1.61.0-beta0
Hi, I believe i've found a potential issue with the new frameworks implemented in atom v1.61.0-beta0. The packages mentioned here fail to load, and each return the same error:
This is my first time attempting to debug an issue like this, but an educated guess from taking a look at the stack traces tells me that this is an issue with atom, or electron. Perhaps a node dependency? Unfortunately, i've hit a wall attempting to fix the problem myself. So i'm opening the issue here in hopes that someone more experienced could see this and provide insight.
Please close this issue and accept my apologies if it turns out to be irrelevant.
The text was updated successfully, but these errors were encountered: