As a developer, I should be able to install echobind's eslint rules in my project

[alvincrespo]

Summary

eb-scripts init --linting

By default, this would include our eslint configuration into a project.

Motivation

Why are we doing this?

To give developers an easy method to setup eslint on their project.

What use cases does it support?

Initializing a new project that enforces consistency.

What is the expected outcome?

• Adds eslint configuration to their package.json
• Adds dependencies to their package.json

[jsjoeio]

What if instead, we packaged our linting inside eb-scripts? You wouldn't have to do anything at all.

[alvincrespo]

Since it's our scripts we can do that and be opinionated - but it comes down to whether we see others wanting that to be installed on their project.

[jsjoeio]

Well, this is intended for us. People wanting to use it would be a side effect (IMO).

We might be able to leverage a similar pattern as the /_templates feature.

1. Include our own implementation of eslint in eb-scripts
2. If a user wants to override, they can add the same file to their root

Thoughts?

[jsjoeio]

I was thinking about it...

I think your original idea makes the most sense.

[jsjoeio]

We would also need a value to know which linting to add (React, Node or React Native)

[jsjoeio]

Another thought that came to mind, you should be able to do this in two ways:

• eb-scripts init --linting <react | react-native | node>
• eb-scripts add --linting <react | react-native | node>

In the first scenario, you're initialing a project and you want to include linting in the process. In the second scenario, you already have a project and want to add the linting.