Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

esnext option doesn't appear to be working #69

Closed
kenwheeler opened this issue Feb 26, 2015 · 5 comments
Closed

esnext option doesn't appear to be working #69

kenwheeler opened this issue Feb 26, 2015 · 5 comments

Comments

@kenwheeler
Copy link

Using the following syntax:

gulp.task('jscs', function(){
  return gulp.src('src/*.js')
      .pipe(jscs({
        esnext: true
      }))
});

I don't get any output. Running jscs --esnext on the CLI reports properly, and using the option with the gulp-jscs-custom module works though.

@LFDM
Copy link

LFDM commented Jun 4, 2015

Same here, unfortunately.

@dsebastien
Copy link

Same here

@geelen
Copy link

geelen commented Jun 29, 2015

And here. Adding esnext: true changes the error from

    14 | fetch(window.location.origin + iceURL)
    15 |  .then(response => response.json())
--------------------------^

to

  line 15  col 24  'arrow function syntax (=>)' is only available in ES6 (use esnext option).

So clearly something is happening...

@geelen
Copy link

geelen commented Jun 29, 2015

Whoops, it was a JSHint error that was running alongside! JSCS seems to be handling arrow functions fine.

@sindresorhus
Copy link
Contributor

Fixed in 3.0.0

Specify it in your JSCS config file.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants