Jshint: ES7 Class Properties throws 'Unexpected token ='

Created on 13 Apr 2015 · 8Comments · Source: jshint/jshint

Jeff Morrison's stage 0 class property initializers proposal fills the void of property composition on classes.

Currently when using:

class Person {
  firstName = 'John'; // jshint error 'Unexpected token ='
  static lastName = 'Doe';
}

console.log(new Person().firstName); // "John"
console.log(Person.lastName); // "Doe"

Any plans to support such feature? Or maybe I'm missing an option? Thanks!

Source

voronianski

Most helpful comment

Just an update, it's at stage 2 now: https://github.com/tc39/proposals. Perhaps time to re-open this issue?

MikeShi42 on 20 Aug 2016

👍12 🎉1

All 8 comments

It would be unwise for JSHint to commit to supporting any stage 0 proposals.

jugglinmike on 13 Apr 2015

You can prevent the error by demarcating non-standard portions with an ignoreDelimiter:

class Person {
  //start-non-standard
  firstName = 'John';
  static lastName = 'Doe';
  //end-non-standard
}

.jshintrc

...
ignoreDelimiters: [
  { start: "start-non-standard", end: "end-non-standard" },
],
esnext: true
...

rwaldron on 13 Apr 2015

@rwaldron thanks!

voronianski on 13 Apr 2015

@voronianski you're welcome!

rwaldron on 13 Apr 2015

It's up to stage 1 now: https://github.com/jeffmo/es-class-static-properties-and-fields
I know that's still not very far along, but I would love to use this without littering my code with start-non-standards in every class!