This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-07
Channels
- # admin-announcements (2)
- # arachne (1)
- # bangalore-clj (2)
- # beginners (39)
- # boot (349)
- # cider (31)
- # clara (2)
- # cljs-dev (9)
- # cljsjs (67)
- # cljsrn (7)
- # clojure (300)
- # clojure-art (4)
- # clojure-greece (11)
- # clojure-hk (3)
- # clojure-israel (1)
- # clojure-italy (17)
- # clojure-japan (1)
- # clojure-russia (33)
- # clojure-sg (2)
- # clojure-spec (41)
- # clojure-uk (86)
- # clojurescript (123)
- # clojurex (3)
- # code-reviews (1)
- # component (6)
- # crypto (1)
- # cursive (36)
- # datomic (32)
- # devcards (3)
- # emacs (11)
- # events (3)
- # funcool (4)
- # luminus (10)
- # om (28)
- # onyx (88)
- # pedestal (2)
- # re-frame (84)
- # reagent (7)
- # ring-swagger (3)
- # specter (33)
- # sql (2)
- # vim (21)
yeah; I just install eslint-babel and other ones I need globally too, to avoid having to set up per project local executables
If I recall correctly, they don’t get invoked unless your project’s config specifies, so they just stay out of the way on other projects
@vinnyataide just configure eslint to the local eslint executable
not the global one
M-x customize-variable flycheck-javascript-eslint-executable
tto /path/to/my/project/node_modules/.bin/eslint
Also watch this thread to see if they fix it properly in eslint: https://github.com/eslint/eslint/issues/1238
but it is locked.
I guess you could also set the variable to "npm run eslint"
so that it can be project independent.
or even alias eslint to npm run eslint so that it behaves on command line too.