chore: Setup eslint for packages/nuqs

[tylersayshi]

Sharing the lint setup I created when debugging #566 in case linting is desired going forward.

This is mostly the default setup from npm init @eslint/config@latest with eslint 8, react, and ts. I added eslint-plugin-react-hooks & eslint-plugin-react-compiler.

I disabled the following rules because they throw errors in the current codebase that I didn't find particularly useful here:

rules: {
  '@typescript-eslint/no-explicit-any': 'off',
  '@typescript-eslint/ban-ts-comment': 'off',
  'no-useless-escape': 'off'
}

I also disabled eslint entirely in the *.test-d.ts files because those threw many errors with the rules of hooks and if the current usage of those files works fine for testing, I don't see any reason to lint there (at least for the rules of hooks).

Lastly, there are just a few warnings related to dependency arrays of the current hook usages:

These can be fixed very easily, but I will wait for feedback on how y'all would like to fix them (or not fix them) before making further changes.

[vercel]

Someone is attempting to deploy a commit to the 47ng Team on Vercel.

A member of the Team first needs to authorize it.

[tylersayshi]

@franky47 should I close this? I'm guessing since it's been left here, you're likely not interested which is np for me, I just like to close things to keep my PR tabs clean if they're not going anywhere.

[franky47]

Yeah I think we can close this. My experience with eslint has always been negative, though I see the value in a linter for community projects.

My eyes are on Biome to replace Prettier & linter steps, but last time I tried it it wasn't quite ready (especially regarding Tailwind support in the docs app).