Jshint: Experimental support for class fields

Any updates on that? It's stage 3 now.

Can this be reviewed, please?

@andrewvaughan This isn't a pull request, so there's no code to review. We've been ready to accept patches for it since I opened the issue, so we don't need to revisit policy, either. All that's needed is for someone to write the code. Might that be you?

I'd be happy to help you get your bearings, of course!

@andrewvaughan This isn't a pull request, so there's no code to review. We've been ready to accept patches for it since I opened the issue, so we don't need to revisit policy, either. All that's needed is for someone to write the code. Might that be you?

Normally I'd be happy to contribute - but, until very recently, JSHint was still functioning in the ES6 realm, which was surpassed nearly three years ago. Given that ES7, 8 and 9 were all supported in a giant patch just a few days ago, I'm not filled with tremendous faith that the project will remain current and my work would be beneficial.

If it were released more incrementally and in-line with the EMCA revisions, I'd be inclined to, but at this point, it makes more sense to strip JSHint from my project and use another linting tool in the meantime.

Best of luck with the project.

The "public class fields" proposal has been merged with one for private class fields. I've updated this feature request's title accordingly.