Closed yusdacra closed 2 years ago
We should keep eslint
and make it a part of nix check
. I could see the argument however to use eslint
from nodePackages
.
We should keep
eslint
and make it a part ofnix check
. I could see the argument however to useeslint
fromnodePackages
.
Yes, I think we can use eslint
from nodePackages
. I will work on that to add a checks
outputs.
@toastal I added a checks output that checks with eslint
and also added eslint
to devshell. I could only make it check frontend-dashboard and frontend-vault since frontend-landing doesn't seem to have a eslint config.
We should open a new issue where we make an ardana-eslint-config
project inside the npm Workspaces where we can share and reference a shared config rather than risking any of these projects looking different.
We should open a new issue where we make an
ardana-eslint-config
project inside the npm Workspaces where we can share and reference a shared config rather than risking any of these projects looking different.
Okay, can this be merged then (after you review) and then we make that issue so we can follow up later?
I had to remove
eslint
from devDependencies becausenpm
was complaining about it. I'm not sure how this matters, but it seems to build fine.