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

Update default JS syntax checker to JSHINT with es6 support enabled #797

Closed
Naatan opened this Issue Nov 4, 2015 · 9 comments

Comments

Projects
None yet
4 participants
@Naatan
Member

Naatan commented Nov 4, 2015

The Mozilla one is dated and does not address common use-cases of modern Javascript, we can still include it but the default should support the newest technologies and jshint is good at that.

Note we currently do not package jshint, so we need to start doing that.

Atm jshint 2.6.0 is the latest version that works, later versions are broken due to lodash/lodash#1493

@Naatan Naatan added this to the 9.4 milestone Nov 4, 2015

@Naatan

This comment has been minimized.

Member

Naatan commented Nov 4, 2015

Fwiw these are the jshint settings I use: moz=true unused=true esnext=true

@Naatan Naatan modified the milestones: 9.4, 10.0 Nov 13, 2015

@Defman21

This comment has been minimized.

Contributor

Defman21 commented Feb 4, 2016

@Naatan 536f1e6 isn't the fix?

@mitchell-as

This comment has been minimized.

Member

mitchell-as commented Feb 4, 2016

It looks like half the fix. It looks like I still need to enable those settings by default.

@Naatan

This comment has been minimized.

Member

Naatan commented Feb 4, 2016

But only for HTML5, not HTML.

As a side-note, we should probably rename those to HTML and HTML4, because HTML5 is the standard now.

@surfyogi

This comment has been minimized.

surfyogi commented Feb 6, 2016

Just to point out from the trenches of Google, I was over there last week and they made some announcements:

ES6 will be called ES2015
ES7 will be called ES2016
ES6 is supported by NodeJS now
Most browsers support most ES2015 features now

Fact is PHP, Java, some .NET, and Ruby to some extent are being eaten alive by NodeJS for server farms. It's 10x less load on servers, and less salaries ($) to manage it. Ebay, Walmart, IBM, Paypal, everybody is moving to it...

Which means I hope, that you will be giving JS support a lot more attention going forward, as it's taking over the landscape here quickly. Easily the most popular language now.

I don't want to have to hack my IDE so it will support ES2015...

@Naatan

This comment has been minimized.

Member

Naatan commented Feb 6, 2016

Thanks for the additional info! :)

I don't want to have to hack my IDE so it will support ES2015..

Of course not, that's what this ticket is all about. JavaScript and everything that it entails will be a primary focus of Komodo 10. See also: http://komodoide.com/blog/jsx-and-react-a-komodo-syntax-highlighting-case-study/

@surfyogi

This comment has been minimized.

surfyogi commented Feb 6, 2016

Good to hear, I was about to purchase 9...
Free upgrades?

@surfyogi

This comment has been minimized.

surfyogi commented Feb 6, 2016

OH yes, and the other announcement:

ES spec will have a new release yearly now, so that specs do take 4 years to write and approve.
Things are really speeding up.. so if a feature doesn't make it 2016, it will be in 2017, but there
is still a new spec without fail.

@Naatan

This comment has been minimized.

Member

Naatan commented Feb 6, 2016

Free upgrades?

Komodo 10 is still a ways off, too early to say anything about upgrades or pricing. So likely if you buy Komodo 9 now you would have to pay to upgrade to 10.

ES spec will have a new release yearly now, so that specs do take 4 years to write and approve.

We'll definitely keep our eye on those. For now the primary focus is on ES6 / ES2015, as that is the most widely used at the current time. Which is not to say we aren't also looking into ES7 / ES2016.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment