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
This change is not strictly necessary, but a unique strength of this codebase is that TypeScript is used on both the frontend and backend. Language consistency will go a long way in speeding up development, but it is essential that your linters maintain that consistency (TypeScript can look very different under different linting rules!).
This may or may not be difficult to do, but reusing things like your ESLint and tsconfigs (if possible) across both stacks could be valuable. Not sure of the best way to implement this, maybe they can be directly reused or just kept in sync somehow...
The text was updated successfully, but these errors were encountered:
I can't find a way to do it besides having node in the root directory instead of separately in the frontend and backend, so I think it's a bit impractical to do at this point. I can look more into it though.
This change is not strictly necessary, but a unique strength of this codebase is that TypeScript is used on both the frontend and backend. Language consistency will go a long way in speeding up development, but it is essential that your linters maintain that consistency (TypeScript can look very different under different linting rules!).
This may or may not be difficult to do, but reusing things like your ESLint and tsconfigs (if possible) across both stacks could be valuable. Not sure of the best way to implement this, maybe they can be directly reused or just kept in sync somehow...
The text was updated successfully, but these errors were encountered: