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

@babel/eslint-* v8 #10752

Open
kaicataldo opened this issue Nov 22, 2019 · 7 comments
Open

@babel/eslint-* v8 #10752

kaicataldo opened this issue Nov 22, 2019 · 7 comments
Labels

Comments

@kaicataldo
Copy link
Member

@kaicataldo kaicataldo commented Nov 22, 2019

Making an issue here to track the work that needs to be done for the new @babel/eslint-* packages for the v8 release.

@babel/eslint-parser (taken from https://github.com/babel/babel-eslint/milestone/1):

@babel/eslint-plugin

  • Can we create a shared config that enables the parser and corresponding rules automatically?
  • Audit current rules to see if they need to exist.
  • Remove deprecated rules?
  • Figure out how we can be more proactive rather than reactive. Run core rules over fixtures that contain new experimental syntax? Fuzzer?

Please feel free to edit this comment or discuss below.

@not-an-aardvark

This comment was marked as off-topic.

Copy link
Member

@not-an-aardvark not-an-aardvark commented Nov 22, 2019

Thanks for working on this!

By the way, mentioning @babel/eslint in a GitHub comment has the effect of pinging the people on the GitHub team with the same name. I don't have a problem with the ping, but just pointing it out since I'm not sure that was the intention.

@nicolo-ribaudo

This comment was marked as off-topic.

Copy link
Member

@nicolo-ribaudo nicolo-ribaudo commented Nov 22, 2019

@hzoo Can we rename the team to @babel/eslint-team?

@kaicataldo

This comment was marked as off-topic.

Copy link
Member Author

@kaicataldo kaicataldo commented Nov 23, 2019

@not-an-aardvark Definitely was not the intention. Sorry about that!

@existentialism

This comment was marked as off-topic.

Copy link
Member

@existentialism existentialism commented Nov 23, 2019

@kaicataldo

This comment has been minimized.

Copy link
Member Author

@kaicataldo kaicataldo commented Nov 23, 2019

Thoughts on this current list? I'd love to evaluate the additional options proposed in the issues above for @babel/eslint-parser in particular.

@kaicataldo

This comment has been minimized.

Copy link
Member Author

@kaicataldo kaicataldo commented Dec 11, 2019

I'm not sure this should be a high priority for the v8 release: babel/babel-eslint#786. While it would be nice to support this, this feels like an edge case that, if we do support, might open up another can of worms. Thoughts?

@kaicataldo

This comment has been minimized.

Copy link
Member Author

@kaicataldo kaicataldo commented Dec 11, 2019

Also wanted to note that we should probably wait for estree/estree#204 to be finalized before updating the ESLint packages so that we don't duplicate any work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.