Add eslint for development

[nvh95]

Is your feature request related to a problem? Please describe.
This comment https://github.com/nvh95/jest-preview/pull/79/files#r865053054 can be avoided by having eslint installed.

Describe the solution you'd like
Integrate eslint for development env

Describe how should jest-preview implements this feature
Install eslint and related plugins (prettier, node, typescript...)

[Rohitbels]

@nvh95 Have you considered any eslint configs you would like to extend?
I can do this.

[nvh95]

@Rohitbels Thanks for your support. Anything not conflict with prettier is fine. I am looking forward to see your PR 🤩

[Rohitbels]

Okay.
So @nvh95
I see we have multiple subdirectories website, examples etc having their own package.json.

We can have eslintrc file for top level that will govern all top level directories not having their own package.json like src, demo, cli, and others.

Every other sub directory having a package.json needs to have its own eslintrc file.

PS: I would like to add going forward this project will need use workspace to improving the maintenance process.

[nvh95]

Thank you @Rohitbels. I am converting this project into pnpm workspace, the progress is tracked in #255

I am not available to finish it yet. But aiming for the next few weeks.

For the current folder which have its own package.json. We might not need eslint for them (?). Since it's kind of "external" ones. For example, websites has nothing to do with jest-preview.

I think you can try to just add eslint for current state of the project, or you can wait a little bit longer after #255 get merged, then add eslint. It's up to you.

Again, thanks for your interested in helping us improve the DX of jest-preview