Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fix JSHint issues

See original GitHub issue

JSHint flags a bunch of suspicious usages when compiling, fix these so that we can compile without using --force

Running "jshint:all" (jshint) task

app/scripts/controllers/containerdetails.js
  line 36   col 8    Missing semicolon.
  line 148  col 23   Expected '!==' and instead saw '!='.

app/scripts/controllers/containerfileviewer.js
  line 86   col 24   'result' is already defined.
  line 118  col 24   'i' is already defined.
  line 134  col 45   Missing semicolon.
  line 227  col 123  Expected '===' and instead saw '=='.
  line 227  col 142  Missing semicolon.
  line 227  col 144  Missing semicolon.

app/scripts/controllers/registerworkflow.js
  line 58   col 28   Expected '!==' and instead saw '!='.

app/scripts/controllers/workflowdagview.js
  line 45   col 39   Expected '===' and instead saw '=='.
  line 121  col 28   'cytoscape' is not defined.

app/scripts/controllers/workflowdetails.js
  line 118  col 53   Missing semicolon.
  line 130  col 23   Expected '!==' and instead saw '!='.
  line 337  col 84   Missing semicolon.

app/scripts/controllers/workflowfileviewer.js
  line 86   col 24   'result' is already defined.
  line 117  col 24   'i' is already defined.
  line 132  col 45   Missing semicolon.
  line 189  col 123  Expected '===' and instead saw '=='.
  line 189  col 142  Missing semicolon.
  line 189  col 144  Missing semicolon.

  ⚠  20 warnings

Warning: Task "jshint:all" failed. Use --force to continue.

Issue Analytics

State:
Created 7 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

jpatriciacommented, Jul 22, 2016

With the package.json and bower.json updated with newer versions of the modules, jshint issue might have been resolved. Locally, I dont have anymore jshint issue. Will need to test on staging and production about this

0reactions

denis-yuencommented, Aug 12, 2016

This looks fixed now

Top Results From Across the Web

Any tool to automatically fix simple JSLint issues? [closed]

Sounds like a bug. Try beautifying your code in two halves (as long as the halving is done at a legal place, parse-wise),...

jshint/fixmyjs: Automatically fix silly lint errors. - GitHub

Programatically. Legacy uses JSHINT to determine what needs to be fixed and then uses a combination of regular expressions and string replacements to...

JSHint Options Reference

JSHint is limiting its scope to issues of code correctness. If you would like to enforce rules relating to code style, check out...

How do I resolve these JSHint ES6 errors?

I'm getting some errors from JSHint that I thought would be fixed by my settings, but they're not. “JSHint: 'self' is not defined....

Finding and Fixing JavaScript errors with JSHint

... issues so that people can “claim” the files they'd like to fix! At the bottom is a list of every file in...