From: Jason Foreman <jason@threeve.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Any hints for JavaScript development?
Date: Sat, 30 Apr 2016 00:13:17 -0500 [thread overview]
Message-ID: <m2oa8rvfv6.fsf@slughorn.attlocal.net> (raw)
In-Reply-To: 87d1p7vhoe.fsf@mbork.pl
Marcin Borkowski <mbork@mbork.pl> writes:
> are there any JS developers here who could share their knowledge/Emacs
> setup? There seems to be a few JS modes out there, and some things are
> not clear to me. For instance, it seems that the features of js2-mode
> and flycheck overlap (I don't use either yet): does it make sense to use
> them both? What are the auto-completion options (besides plain vanilla
> Emacs or things like ivy/helm/icicles and e.g. company)? Any other
> hints? (I guess I should probably look at skewer-mode; any others?)
Spacemacs' layer for javascript is a good starting reference:
https://github.com/syl20bnr/spacemacs/blob/master/layers/%2Blang/javascript/packages.el#L12
While there may be some small overlap between js2-mode and flycheck
you'll most likely want them both: js2-mode gives you font lock and
indentation and potentially some syntax checking, but flycheck can hook
into a wide array of external tools that go beyond what js2-mode
provides.
Tern + company-tern appears to be the way to go for semantic
autocompletion, unless you're using Flow or Typescript in which case
those can also provide completion via their packages.
next prev parent reply other threads:[~2016-04-30 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 4:34 Any hints for JavaScript development? Marcin Borkowski
2016-04-30 4:50 ` Emanuel Berg
2016-04-30 5:05 ` Emanuel Berg
2016-04-30 5:13 ` Jason Foreman [this message]
2016-04-30 10:19 ` Raspbian, Debian and Emacs/LaTeX repositories Emanuel Berg
[not found] ` <mailman.1588.1461993634.7477.help-gnu-emacs@gnu.org>
2016-05-01 7:13 ` Any hints for JavaScript development? Sayth Renshaw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2oa8rvfv6.fsf@slughorn.attlocal.net \
--to=jason@threeve.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.