ESLint to force @types in dev-dependencies
We recently had an outage coz someone installed the @types/[package-name] in dependencies, but never installed the actual package itself. Particularly, they installed
@types/imurmurhash in dependencies, but didnt install imurmurhash itself (and no one reviewing noticed it in the PR). Our no-extraneous-dependencies rule in ESLint didnt catch this coz the type declarations were present.
Had the @types/ been installed in dev-dependencies, ESLint would have caught the missing dependency issue. Anyway to use to ESLint to check @types / packages are dev-dependencies and not dependencies ?
I can raise an issue in ESLint, but was wondering if getting a solution might be faster here.21KMembers
View on DiscordWant results from more Discord servers?
More PostsUpdating existing T3 with Supabase Auth from Next AuthBackground:
- Launched a T3 app with Next Auth.
- Currently got 3000 users.
- Launching an app vetRPC + AppRouter without reactQueryhi everyone how can i host trpc on next.js and use trpc on server components without using react queMutate instantly returning success instead of isLoadingI have been working on this endpoint that uploads files do Google Drive. It can upload one or multipNext 13.4 problem with loading state after content is visible & hydration problemHey, I have a small app with Next 13.4 with Shadcn Ui 😍 it's really really good.
But I'm also using