summaryrefslogtreecommitdiff
path: root/.dir-locals.el
diff options
context:
space:
mode:
authorMarkus Heiser <markus.heiser@darmarit.de>2021-11-20 17:00:07 +0100
committerMarkus Heiser <markus.heiser@darmarit.de>2021-11-20 17:08:22 +0100
commit5242a841a5dd2179d1ed620a67594932eb129422 (patch)
treed098a709cf5c7a8b0d0c535b6b094a3a0b3a5a31 /.dir-locals.el
parent69dd025da904e5f067e234d9b65d1a8a3ea8fdab (diff)
[mod] NVM: dev-tools pre-installed in NVM's node installation
The Node.js installation in the NVM environment can be used by IDEs and other developer tasks. The required developer packagaes are added to the file ./.nvm_packages and will be installed when Node.js is installed. Initial we start with: - eslint Having a dedicated developer enviroment, provided by nvm makes it easy to integrate Node.js packages into various IDEs. One example is shown in the .dir-locals.el which is used by emacs. [1] https://github.com/nvm-sh/nvm#default-global-packages-from-file-while-installing [2] https://eslint.org Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Diffstat (limited to '.dir-locals.el')
-rw-r--r--.dir-locals.el5
1 files changed, 1 insertions, 4 deletions
diff --git a/.dir-locals.el b/.dir-locals.el
index e1d0b8ef..f67ab471 100644
--- a/.dir-locals.el
+++ b/.dir-locals.el
@@ -94,12 +94,9 @@
(js-mode
. ((eval . (progn
- ;; flycheck should use the (local) NVM environment (see nvm-dir)
+ ;; use nodejs from the (local) NVM environment (see nvm-dir)
(nvm-use-for-buffer)
(setq-local js-indent-level 2)
- ;; flycheck should use the eslint checker from simple theme
- (setq-local flycheck-javascript-eslint-executable
- (expand-file-name "searx/static/themes/simple/node_modules/.bin/eslint" prj-root))
(flycheck-mode)
))))