You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
typescript-eslint could be very useful if we decide to migrate the codebase to TypeScript.
Using TypeScript would also simplify writing package code that auto-generates types, improving the experience for consumers.
That said, a migration to TypeScript should be discussed in a dedicated issue.
I think it’s something we should consider after publishing the first version of the packages,
(using declaration files generated from JS via JSDoc).
we’re currently using:
We might need to add more plugins:
typescript-eslintcould be very useful if we decide to migrate the codebase to TypeScript.Using TypeScript would also simplify writing package code that auto-generates types, improving the experience for consumers.
That said, a migration to TypeScript should be discussed in a dedicated issue.
I think it’s something we should consider after publishing the first version of the packages,
(using declaration files generated from JS via JSDoc).
vitesteslint plugin (pending test(backend): migrate to vitest #95)nodeeslint plugin forapps/backend