Can't get it going... :( about atom-jshint

[Joezo]

Which version are you using and which version of the plugin are you trying to install?

[william-index]

After a certain update of Atom, it stopped working for me as well.

OSX 10.9.3
Atom: Version 0.115.0 (0.115.0)
Atom Jshint 1.4.3

It is installed, and worked on a previous version of atom, but ceased functioning after the update.
If something (a conditional for example) is left open, it will open atoms console and show parse errors (so it is trying to do its job), but it will not show errors/warnings form linting.

[Joezo]

Are you able to provide a stack trace from the console that pops open? That'd be really handy!

[joepagan]

Sure, though wont be till Weds as the problem is with my iMac at work.

Cheers,

On 21 July 2014 23:26, Joe Warren [email protected] wrote:

Are you able to provide a stack trace from the console that pops open?
That'd be really handy!

—
Reply to this email directly or view it on GitHub
#44 (comment).

[william-index]

When parsing script that is unfinished such as an open conditional such as:

$(document).ready(function(){
   if(1==2){
});

I will get a console error such as:

Uncaught Unexpected token: punc ()) (line: 3, col: 1, pos: 43)

Error
at new JS_Parse_Error (/Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:196:18)
at js_error (/Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:204:11)
at croak (/Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:663:9)
at token_error (/Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:671:9)
at unexpected (/Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:677:9)
at /Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:761:17
at /Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:710:24
at block_ (/Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:984:20)
at /Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:957:25
at function_ (/Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:962:15) /Users/wanderson/.atom/packages/atom-auto-uglify/node_modules/uglify-js/lib/parse.js:204

Otherwise code such as

$(document).ready(function(){
    if(1==2){
        console.log()
    }
});

no longer shows any warnings on the screen window log area on Atom. This worked before, and on this machine, the OS has not been updated though atom has.

[Joezo]

Okay, that stack trace looks like an error in the 'atom-auto-uglify' package. If you disable that do you still get the error?

[william-index]

Sorry about that. When disabled, I get an error for jshint when a statement is unfinished/missing a closing curly

Uncaught TypeError: Cannot call method 'getBuffer' of undefined /Users/wanderson/.atom/packages/atom-jshint/lib/atom-jshint.js:58

[joepagan]

Turns out I don't even get the console popping open:

[joepagan]

bump

[Joezo]

Sorry - I should of gotten back to you sooner here, what is the actual problem you're getting? It's just plain not working or you're getting errors? Perhaps you have other packages installed that conflict with this one. Maybe try disabling others that you have installed and see if this one then works.

[william-index]

After disabling all other plugins except for this one and the ones default to atom on install. It still does not work on any file I download, create, import/etc. Except it DOES work when viewing its own source in github, but only when opening that file.

Even having the same code in a new .js document does not perform linting.

To me it looks as though it simply isnt even checking through any other files.

[joepagan]

I just get absolutely nothing like @william-index is getting. Though haven't tried the suggested file in that repo yet. Will give that a shot tomorrow.

[kwazi]

I'm experiencing the same issue, atom-jshint is the only additional (non default) plugin I have enabled, and it doesn't work. It definitely used to work but atom seems to have updated since then, and now it doesn't work.

However, just like @william-index , if I try to view it's source, it works... weird.

Atom v0.120
Running OS X 10.9
Atom-Jshint 1.4.3

[Joezo]

I'm really not sure what's causing that to happen, when I get a chance i'll try it out on a fresh installation of Atom and see if I can replicate it. Because at the moment i cannot :(

[mkleehammer]

I haven't seen it working in weeks either. Does it require a config file or anything to start working?

[Joezo]

I think you might be on to something with that comment. That would explain it only working when editing a file belonging to this project. Could one of you see if adding a jshintrc file solves the problem? I'll try to sort it out so that it defaults to the default... if it does indeed need one :)

[ponychicken]

I deleted all installed packages and reinstalled only jshint and it still doesn't want to work.

[ponychicken]

Adding a jshintrc didn't change anything

[pajtai]

same here, no errors showing with a .jshintrc file and a js file filled with gibberish

[xealgo]

MacbookPro, Atom-jshint 1.4.3. same issue. Not running for me at all either.

[jladuval]

I too am getting this issue. Macbook pro Atom version 0.132

[sjurba]

Did you check the console? Alt cmd i. 

The .jshontrc file might be malformed. Its very strict about quoting keys, trailing commas, etc..
—
Sjur

On Thu, Aug 28, 2014 at 12:43 AM, Peter Ajtai [email protected]
wrote:

same here, no errors showing with a .jshintrc file and a js file filled with gibberish

Reply to this email directly or view it on GitHub:
#44 (comment)

[mwq27]

Same problem, nothing is happening when the plugin is enabled. No errors or warnings are showing in the console. Atom v1.4.3

[codyhazelwood]

Same issue here. I've been using the plugin for months with no issues, but with one of the recent atom updates, there's no feedback. Nothing shown in the console either. Atom v0.136.0. I have a .jshintrc file in the root directory of each project.

[lvivier]

Same issue here. Nothing in the console, just not working anymore:

• OS X 10.9.4
• Atom 0.136.0
• Atom Jshint 1.4.3

[Joezo]

This may have been fixed by #60 please reopen if not the case :)