linter-js-standard: Repeated alerts saying "Something went wrong internally"

screen shot 2016-07-22 at 13 59 05

I’m seeing a lot of this warning appearing when I edit files in Atom using this plugin. A couple of things:

  1. The warning is sufficiently vaguely worded that I at first mistook it for an Atom issue itself. When informed on the Atom.io Slack channel that there was nothing in Atom itself that would issue such a dialog, then I searched the .atom folder and found this:
$ grep -rlIn "this annoying warning" .
./packages/linter-js-standard/lib/linter-js-standard.js
./packages/linter-js-standard/lib/utils/style-settings.js
  1. This happens really frequently in some files, never on others. I have no idea what’s different. Seems to have started when I installed Atom 1.8.0 (another reason I was inclined to blame Atom at first)

  2. Closing and reopening the file never helps.

LMK if there’s more detail I can provide.

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Reactions: 16
  • Comments: 27 (4 by maintainers)

Most upvoted comments

I fixed it by doing this:

File > Settings > Packages > Search "linter-js-standard" > Click Disable > Click Enable > Restart Atom.io

tumblr_mtud5kx2t71r7fahjo1_250

This started happening for me after updating packages after not having done so in a while.

Check/uncheck each setting checkbox then back to your setting.

This fixed it. 😃

Can the code for that alert just be removed? I’m going to have to remove this package or fork it.

@sonicdoe I am no longer experiencing this warning. Currently using linter-js-standard@3.9.2.

Hi all, in the meantime, if you want a solution for this problem, I suggest to uninstall this package and install linter-js-standard-engine instead. Worked for me, I don’t get the yellow error popups any more.

Just have the standard installed as a devDependency and it will be tapped OK. I suggest not to use * semver range but update it manually. Last major release (v10) introduced new rules (like import being not at the top) that broke previously valid v9 code.

This error is appearing even when editing non-js files for me. Almost any file that I open and again on every save unless I close, reopen and re-save the file.

Hutch your suggestion doesn’t fix this for me.

I’ve been getting the same problem relentlessly in certain projects.

Opening the devtools shows the following error having been thrown:

Uncaught (in promise) Error: Something went wrong.
    at Object.checkStyleSettings (/Users/jimobrien/.atom/packages/linter-js-standard/lib/utils/style-settings.js:54:13)
    at Object.module.exports.__cacheTextEditor (/Users/jimobrien/.atom/packages/linter-js-standard/lib/init.js:101:21)
    at storeSettings (/Users/jimobrien/.atom/packages/linter-js-standard/lib/init.js:64:14)
    at /Users/jimobrien/.atom/packages/linter-js-standard/lib/init.js:71:7