-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to activate the atom-beautify package #2342
Comments
I can confirm the same issue is occurring for me on Manjaro. |
I have the issue as well.
Atom: 1.36.0 x64 Stack TraceFailed to activate the atom-beautify package
Commands
Non-Core Packages
|
Same thing for me on Arch Linux. I've got the same stack trace output, etc., so I'll skip pasting it here, so the issue doesn't get too long with almost identical pastes. ;) |
This seems to be a problem with one of the dependencies: prettier and not atom-beautify itself. It does a very strange eval() call, which seems to be redundant and from what I understand from the upstream issue, it's generated by a parser that's used to build the project. Upstream issue: prettier/prettier#6053 WorkaroundFire up the ~/.atom/packages/atom-beautify/node_modules/prettier/index.js file (possible line numbers: 33160, 40204 or 40747 - as stated in the comments below) and change: After restarting the stack trace will go away and atom-beautify will function normally until an update is available. 😄 |
@TeHMoroS For me it was in line 40747 :) |
for me was the line 40204 |
[Enter steps to reproduce:]
Atom: 1.36.0 x64 Stack TraceFailed to activate the atom-beautify package
Commands
Non-Core Packages
|
Same here. @TeHMoroS workaround totally worked! The line number was |
There is comment in ~/.atom/packages/atom-beautify/node_modules/prettier/index.js says: // plugin will look for `eval("require")()` and transform to `require()` in the bundle,
// and rewrite the paths to require from the top-level.
// We need to list the parsers and getters so we can load them only when necessary. 🤔 |
Sorry forgot to reply. The edit fixed my problem. I was 40747. Thanks!! |
@TeHMoroS workaround worked for me too! Thanks! The line number was 40635 :) |
Same issue happening for me on Arch Linux @TeHMoroS 's fix worked for me as well, line 40747 |
@TeHMoroS could it be because of not having installed the formatter |
Help me! [Enter steps to reproduce:]
Atom: 1.36.1 x64 Stack TraceFailed to activate the atom-beautify package
Commands
Non-Core Packages
|
@marcelloinfoweb
|
Are you changing the file at |
Yes, when I opened the file, it was this way, I did not make any changes. I removed the extension, rebooted Atom and reinstalled, now it seems to be working fine. If you come back to give the mistake, I'll come back here with the problem, okay? Thanks for listening! |
[Enter steps to reproduce:]
Atom: 1.40.1 x64 Stack TraceFailed to activate the atom-beautify package
Commands
Non-Core Packages
I tried finding the line index.js in the prettier folder and this is what I got: http://prntscr.com/p4q6aa |
[Enter steps to reproduce:]
Atom: 1.41.0 x64 Stack TraceFailed to activate the atom-beautify package
Commands
Non-Core Packages
|
Tried uninstall, reinstalling multiple times, restarting Atom, installing from gui or |
Did anyone get a solution? I have the same error [Enter steps to reproduce:]
Atom: 1.46.0 x64 Stack TraceFailed to activate the atom-beautify package
Commands
Non-Core Packages
|
OS: Microsoft Windows 10 Enterprise Stack Trace Failed to activate the atom-beautify package Has Anyone find a Solution ? Cannot find module './winston/transports'
|
Same Issue I uninstalled. |
[Enter steps to reproduce:]
Atom: 1.36.0 x64
Electron: 4.1.1
OS: "Manjaro Linux"
Thrown From: atom-beautify package 0.33.4
Stack Trace
Failed to activate the atom-beautify package
Commands
Non-Core Packages
The text was updated successfully, but these errors were encountered: