Atom-beautify: Uncaught Error: Cannot find module './config/cli-config'

Created on 20 Apr 2017  路  10Comments  路  Source: Glavin001/atom-beautify

[Enter steps to reproduce:]

  1. ...
  2. ...

Atom: 1.16.0 x64
Electron: 1.3.13
OS: Microsoft Windows 7 Ultimate
Thrown From: atom-beautify package 0.29.23

Stack Trace

Uncaught Error: Cannot find module './config/cli-config'

At module.js:457

Error: Cannot find module './config/cli-config'
    at Module._resolveFilename (module.js:455:15)
    at Module._resolveFilename (~/AppData/Local/atom/app-1.16.0/resources/electron.asar/common/reset-search-paths.js:35:12)
    at Function.Module._resolveFilename (/app.asar/src/module-cache.js:383:52)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (/app.asar/src/native-compile-cache.js:50:27)
    at /packages/atom-beautify/node_modules/winston/lib/winston/config.js:47:17)
    at Module._compile (/app.asar/src/native-compile-cache.js:109:30)
    at /app.asar/src/compile-cache.js:216:21)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (/app.asar/src/native-compile-cache.js:50:27)
    at /packages/atom-beautify/node_modules/winston/lib/winston/common.js:15:14)
    at Module._compile (/app.asar/src/native-compile-cache.js:109:30)
    at /app.asar/src/compile-cache.js:216:21)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (/app.asar/src/native-compile-cache.js:50:27)
    at /packages/atom-beautify/node_modules/winston/lib/winston.js:24:26)
    at Module._compile (/app.asar/src/native-compile-cache.js:109:30)
    at /app.asar/src/compile-cache.js:216:21)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (/app.asar/src/native-compile-cache.js:50:27)
    at /packages/atom-beautify/src/logger.coffee:10:13
    at /packages/atom-beautify/src/logger.coffee:4:18)
    at /packages/atom-beautify/src/logger.coffee:1:1)
    at Module._compile (/app.asar/src/native-compile-cache.js:109:30)
    at /app.asar/src/compile-cache.js:216:21)
    at Module.load (module.js:473:32)

Commands

     -2:43.8.0 tree-view:show (atom-workspace.workspace.scrollbars-visible-always.theme-atom-dark-syntax.theme-one-light-ui)
     -0:53.5.0 settings-view:install-packages-and-themes (input.hidden-input)
     -0:40.7.0 core:confirm (input.hidden-input)

Non-Core Packages

arduino-syntax 0.0.0 
atom-beautify 0.29.23 
autocomplete-clang 0.11.1 
build 0.67.0 
busy 0.7.0 
file-icons 2.1.3 
gpp-compiler 3.0.7 
intentions 1.1.2 
language-arduino 0.4.3 
language-ini 1.19.0 
language-ino 0.2.0 
linter 2.1.4 
linter-clang 4.1.1 
linter-gcc 0.7.1 
linter-php 1.3.2 
linter-shellcheck 1.4.4 
linter-ui-default 1.2.3 
minimap 4.27.1 
php-cs-fixer 4.1.0 
php-integrator-autocomplete-plus 1.4.0 
phpcbf 0.2.1 
platformio-ide 2.0.0-beta.2 
platformio-ide-debugger 1.0.0 
platformio-ide-terminal 2.5.0 
symbols-tree-view 0.14.0 
tool-bar 1.1.0 
duplicate third-party-bug

Most helpful comment

Type-o in my code caused it. Figured it out.
Thanks

All 10 comments

All was working well and then out of the blue Beautify had an issue... Tried to restart then restart the PC. Uninstall... Reinstall the package and still the error

Please follow the issue template provided. More specifically, adding a link to the required debug.md Gist which includes debugging information that answers our most commonly asked questions.
Thank you.

I think this is a duplicate of https://github.com/Glavin001/atom-beautify/issues/1444

Looks like a Winston issue: https://github.com/winstonjs/winston/blob/de69bccf957cca2247ef529c2b66c88059adbae6/lib/winston/config.js#L47-L49

From the logs 馃憞 :

at /packages/atom-beautify/node_modules/winston/lib/winston/config.js:47:17)

Do you see any files in directory ~/.atom/packages/atom-beautify/node_modules/winston/lib/winston/config/ ?

It is either an apm issue or a winston issue causing problems with installation. I do not know why it is happening only for you and not others.

@davidtaylorjr said the following fixed it for him:

I did a global install of Winston using NPM and it resolved the issue. Package workign great.

I'm going to close this as a duplicate of https://github.com/Glavin001/atom-beautify/issues/1444 and https://github.com/electron/electron/issues/8346 since the cause is the same.

Nevermind.. After hours of trying I've removed Atom completely and now re-installing

Sorry to hear Atom and Atom-Beautify are causing you such problems. This is the second time Winston has caused this issue. I'm not sure if it is apm or Winston, but maybe we should move off of Winston. Thanks for your patience!

Now after removing/un-installing Atom.. Deleting all Atom folders I could find... A new issue with Atom-Beautify.
Parsing: C:\Users\marc\AppData\Local\Temp\input117320-5936-bdfen1.yb0zoajor as language CPP C:\Users\marc\AppData\Local\Temp\input117320-5936-bdfen1.yb0zoajor:20 Error: Unexpected ')' for 'VBRACE_OPEN', which was on line 20 C:\Users\marc\AppData\Local\Temp\input117320-5936-bdfen1.yb0zoajor:31 Error: Unexpected '}' for 'VBRACE_OPEN', which was on line 20 C:\Users\marc\AppData\Local\Temp\input117320-5936-bdfen1.yb0zoajor:18 Unmatched BRACE_OPEN C:\Users\marc\AppData\Local\Temp\input117320-5936-bdfen1.yb0zoajor:18 Unmatched BRACE_OPEN

Glad to hear the installation issue is gone now. I am having trouble understanding your next issue.

If this is a new and unrelated issue, please feel free to create another Issue (of course, first search for similar issues).

Also make sure to provide a debug.md Gist so I can help:

Please follow the issue template provided. More specifically, adding a link to the required debug.md Gist which includes debugging information that answers our most commonly asked questions.
Thank you.

Type-o in my code caused it. Figured it out.
Thanks

had the same issue and fixed it with npm install -g cli-config

Was this page helpful?
0 / 5 - 0 ratings