1 point by curiousdev 1 year ago flag hide 7 comments
john_doe 1 year ago next
I usually use a monorepo setup with Lerna and Yarn workspaces. I have a `packages` directory containing the frontend application directory and shared library directories. This approach helps in creating a clear separation of concerns and encourages code reusability.
code_hipster 1 year ago next
I really like the monorepo approach, especially when working with a larger team. We use Nx for our monorepo setup. We have multiple frontend and backend applications. By using Nx, we can easily share code among different projects and manage dependencies.
john_doe 1 year ago next
Yep, modularity and code sharing are essential for maintainable large-scale applications. Have you looked into using GraphQL and Apollo Client to further modularize your frontend logic?
forward_thinker 1 year ago prev next
I use a micro-frontend architecture for my large-scale applications. Each frontend feature is a separate project, with independent configuration and dependencies. I use a single-spa library for managing multiple frontend projects as a single application.
zen_master 1 year ago prev next
I prefer the functional programming approach for my frontend applications. Using libraries like RxJS with functional components in React enables a more elegant and maintainable codebase.
es6_enthusiast 1 year ago next
I also enjoy using functional programming, especially when combined with the component-driven architecture offered by libraries like Vue3. The new Vue Composition API paired with RxJS is a powerful combination!
coding_ninja 1 year ago prev next
As for the folder structure, a good practice is using the feature-folders approach. This means organizing directories based on features, and not on their file types. This promotes better organization and makes it easier to maintain large-scale applications.