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

added state.ES6 option check; bumped dependencies #51

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

drom
Copy link

@drom drom commented Aug 21, 2015

bumped esutils and esprima version for the ES6 stuff
added state.ES6 property check
bumped eslint version and fixed rules to pass
bumped the rest of the packages for the sake of bumping it

@drom drom changed the title added state.ES6 option chack; bumped dependencies added state.ES6 option check; bumped dependencies Aug 21, 2015
@drom drom mentioned this pull request Aug 21, 2015
invalidExpr(1, strictFE(exprStmt({type: "Identifier", name: "let"})));
invalidExpr(1, strictFE(exprStmt({type: "Identifier", name: "yield"})));
// invalidExpr(1, strictFE(exprStmt({type: "Identifier", name: "let"})));
// invalidExpr(1, strictFE(exprStmt({type: "Identifier", name: "yield"})));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are these disabled?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two fail with esutils v2.0.2 In order to use latest version of esutils I have to comment it out.

@michaelficarra
Copy link
Member

This is a good start, but of course there's so much more that needs to be done for full ES6 support.

@drom
Copy link
Author

drom commented Aug 22, 2015

No doubt. Much more needs to be done 😎

@drom
Copy link
Author

drom commented Aug 22, 2015

Looks like we need to update esutils to progress with ES6.

@michaelficarra
Copy link
Member

Yes, I'm sure esutils will need some updates, but not for the purposes of this PR.

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

Successfully merging this pull request may close these issues.

2 participants