markwainwright / atom-linter-coffee-variables Goto Github PK

1. install the package
2. close and reopen Atom

Atom Version: 1.1.0
System: Mac OS X 10.10.5
Thrown From: linter-coffee-variables package, v0.4.0

Stack Trace

Failed to load the linter-coffee-variables package

At Cannot read property 'debug' of undefined

TypeError: Cannot read property 'debug' of undefined
    at Object.<anonymous> (/Users/nick/.atom/packages/linter-coffee-variables/lib/debug.coffee:2:50)
    at Object.<anonymous> (/Users/nick/.atom/packages/linter-coffee-variables/lib/debug.coffee:1:1)
    at Module._compile (module.js:428:26)
    at Object.defineProperty.value [as .coffee] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:169:21)
    at Module.load (module.js:353:32)
    at Function.Module._load (module.js:308:12)
    at Module.require (module.js:363:17)
    at require (module.js:382:17)
    at Object.<anonymous> (/Users/nick/.atom/packages/linter-coffee-variables/lib/linter-coffee-variables.coffee:1:9)
    at Object.<anonymous> (/Users/nick/.atom/packages/linter-coffee-variables/lib/linter-coffee-variables.coffee:1:1)

Config

{
  "core": {
    "ignoredNames": [
      ".git",
      ".svn",
      ".DS_Store"
    ],
    "disabledPackages": [
      "terminal-status",
      "change-case",
      "debugger",
      "web-browser",
      "js2coffee",
      "filetype-color",
      "atom-color-highlight"
    ],
    "themes": [
      "one-dark-ui",
      "oceanic-next"
    ]
  }
}

Installed Packages

# User
atom-handlebars, v1.2.0
atom-pair, v2.0.10
devdocs, v0.2.1
file-icons, v1.6.11
highlight-selected, v0.10.1
language-babel, v0.15.12
language-cjsx, v0.3.0
language-elm, v1.2.0
language-swift, v0.4.0
linter, v1.10.0
linter-coffee-variables, v0.4.0
linter-coffeelint, v1.1.2
linter-eslint, v3.2.1
oceanic-next, v0.1.2
react-snippets, v0.2.0
regex-railroad-diagram, v0.10.4
remote-atom, v1.2.7
set-syntax, v0.3.0

# Dev
No dev packages

I expect these to be underlined in red.

Also have ticket the debug option under settings but can't find output debug anywhere.

It doesn't seem to do anything when you have JSX in your coffee file.
Coffeelint has the transforms options that makes this possible: https://github.com/clutchski/coffeelint/blob/master/doc/user.md#how-do-i-use-jsx-reactjs
I'll try to look for a solution.

When using atom.workspace the warning "atom" is not defined shows up. Is this unnecessary?

If a file contains a defined but never used error, the plugin highlights the first use of that variable name in the file as the culprit, which isn't accurate in files that use the same variable name in multiple places.

Example:

1   window.doSomething()
2    .then (response) -> response.foo
3    .then (response) -> 'bar'

Expected result:

• 'Unused' error on line 3

Actual result:

• 'Unused' error on line 2

Hello,
it would be nice to be able to set globals at the plugin config:
http://eslint.org/docs/user-guide/configuring#specifying-globals

Is it planned to add this feature in an upcoming version? :-)

Not sure if this is entirely this libs fault or maybe normal coffee lint. While every thing seems to be fine ; I constantly have been seeing comments make atom come to a crawl. Not sure why this is so hard on the system. Again not really sure how to help you except maybe output the stack of packages I have installed.

This should skip .cson files…

Thanks for starting this project!

Instead of modifying the settings in atom.io I think the package should pick up the settings from a projects .eslintrc.

happens on latest version

Not sure if this is possible with eslint / jshint but warning for function args seems to be a contest with how my team works. I personally don't really mind it; but to compromise with them warning only non function argument vars would be useful.

I think some other es6 tools allow you do a comment /* global */

Awesome package btw!

I need to distinguis between "unused vars" and "undefined"

I would like to be able to disable the former or to make an ERROR the latter so that it's different from a plain warning. Does this make sense ?

As you can see, a very big bug and the reason i uninstalled this. Doesn't work if i put it on the next line either.