Does JSHint support async/await?

前端 未结 4 1225
别跟我提以往
别跟我提以往 2020-12-09 00:49

I\'m using JSHint for the JavaScript project (with the Visual Studio Code). And in this project I use async / await, which JSHint highlights as errors.

I tried to se

相关标签:
4条回答
  • 2020-12-09 01:22

    The OP asked it there were any workarounds. It's a kludge, but I've replaced all my 'async' or 'await' with 'async /**/' and 'await /**/'. Then a quick script to swap them into '/*async*/' and '/*await*/' allows me to check with jshint.

    It's not pretty, but it feeds the bulldog.

    0 讨论(0)
  • 2020-12-09 01:34

    Note: Using the forked JSHINT-ESNEXT package (NPM, and github) as suggested in the "accepted answer" requires the inclusion of the "experimental" option to be set.

    /* experimental: [asyncawait] */

    or

    /* experimental: [asyncawait, asyncreqawait] */

    See the source code here for details.

    0 讨论(0)
  • 2020-12-09 01:36

    Update (February 2019) : Async/await are now supported as of version 2.10.1. Simply update your .jshintrc to use "esversion": 9. (+Info : Version changelog)


    Update (july 2018) : Async/await will arrive with the release of JsHint 2.10.0. +info : https://github.com/jshint/jshint/pull/3273


    The JSHINT developing community considers that:

    • JSHINT should first support all the ES6 syntax before start implementing ES7 features.
    • Async Functions are only at stage 1, so the syntax can change a lot

    JSHINT-ESNEXT (PACKAGE)

    However, there is an unnoficial JSHINT package, wich contains experimental support for await/async, called JSHINT-ESNEXT.

    The author, @marcominetti, used the official JSHint 2.7 Master branch and introduced this ES7 feature, taken from the Seb Vincent esnextnext branch.

    Check the Npm Package, and the source in github

    Installation: $npm install -g jshint-esnext

    Right now (Jul 2017) this is the only decent available approach to support await/async in JSHINT.


    JSHINT IGNORE (DIRECTIVE)

    A common suggested workaround or mitigation practice, is using the JSHINT ignore directives.

    // Code here will be linted with JSHint.
    /* jshint ignore:start */
    // Code here will be ignored by JSHint.
    /* jshint ignore:end */
    

    Or:

    ignoreThis(); // jshint ignore:line
    

    I personally find this mitigation practice, dirty and confusing, when our code has a big amount of async/await references. But more confusing and dirty are the JSHINT warnings and errors ;)

    0 讨论(0)
  • 2020-12-09 01:41

    Does jshint support async/await yet?

    No, not yet as of early 2017.

    It appears that it does not yet support async/await. Folks working on jsHint have decided not to support async/await until standards were in a late stage (having apparently been burned previously by supporting things too early when they were still changing) - though implementations already exist (Babel, nodejs, etc...).

    If you follow this jsHint open issue thread, it is still an open issue as of recent comments 7 and 11 days ago.

    And if not, are there any workarounds?

    As of July 2017, there appears to be a fork of the jsHint code called jshint-esnext that has support for async/await here: https://www.npmjs.com/package/jshint-esnext.

    0 讨论(0)
提交回复
热议问题