Pub workspaces 로 monorepo 구성하기 @jaichangpark 1

박제창 Flutter Seoul GDG Golang Korea 2

3

4

5

6

“ Pub now supports shared resolution between packages in a monorepo, or workspace. A workspace is a tightly related group of packages developed, resolved, and released together. — Announcing Dart 3.6 7

dart pub 8

9

In version-control systems, a monorepo ("mono" meaning 'single' and "repo" being short for 'repository') is a software-development strategy in which the code for a number of projects is stored in the same repository. This practice dates back to at least the early 2000s, when it was commonly called a shared codebase. Google, Meta, Microsoft, Uber, Airbnb, and X all employ very large monorepos with varying strategies to scale build systems and version control software with a large volume of code and daily changes. a software-development strategy Monorepo 10 @source: https://en.wikipedia.org/wiki/Monorepo

Monorepo : Advantages dependency management In a multiple repository environment where multiple projects depend on a third-party dependency, that dependency might be downloaded or built multiple times. In a monorepo the build can be easily optimized, as referenced dependencies all exist in the same codebase. code reuse Similar functionality or communication protocols can be abstracted into shared libraries and directly included by projects, without the need of a dependency package manager. Collaboration across teams In a monorepo that uses source dependencies (dependencies that are compiled from source), teams can improve projects being worked on by other teams. This leads to flexible code ownership. 11 @source: https://en.wikipedia.org/wiki/Monorepo

Monorepo : disadvantages More storage needed by default With split repositories, you fetch only the project you are interested in by default. With a monorepo, you check out all projects by default. This can take up a significant amount of storage space. While some versioning systems have a mechanism to do a partial checkout, doing so defeats some of the advantages of a monorepo. Loss of version information Although not required, some monorepo builds use one version number across all projects in the repository. This leads to a loss of per-project semantic versioning. 12 @source: https://en.wikipedia.org/wiki/Monorepo

전환 또는 도입은 언제나 (옵션)선택사항 ● 앱이 점점 슈퍼 앱이 되어가고 있다면 ● 협업하는 팀원이 늘어나고 있다면 ● 커스텀이 필요한 네이티브 패키지 개발이 필요하다면 ● 커스텀 패키지의 소스 오픈이 제한되어 있다면 ● n개의 앱(하나이상의 앱)이 동일한 로직(ex:도메인 또는 데이터 모델)을 사용하고 있다면 언제 도입하는게 적절할까요? Monorepo 13

그렇다면 기존에는? Monorepo 14

Monorepo 15 ● firebase/flutterfire ● Flame-Engine/Flame ● cfug/dio ● simolus3/drift ● FlutterGen/flutter_gen Melos

Monorepo 16 Melos ● Automatic versioning & changelog generation. ● Automated publishing of packages to pub.dev. ● Local package linking and installation. ● Executing simultaneous commands across packages. ● Listing of local packages & their dependencies.

Full-Stack 17 Backend Dart Server Shared Models APIs Front Flutter App (Client)

Pub workspaces 18

The pub workspaces feature ensures that packages in a monorepo share a consistent set of dependencies. This forces you to resolve dependency conflicts between your grouped packages as they arise, rather than facing confusion when you start using the packages. The Flutter analyzer processes all of the packages in a pub workspace in a single analysis context, as opposed to the previous behavior of a separate context for each package. For large repositories, this can significantly reduce the amount of memory the Dart language server consumes, improving IDE performance. monorepo support Pub workspaces 19 @source: https://medium.com/dartlang/announcing-dart-3-6-778dd7a80983

20

Today.. 21

flutter create my_app 22

23 📦my_app ┣ 📂lib ┃ ┗ 📜main.dart ┣ 📜.gitignore ┣ 📜.metadata ┣ 📜README.md ┣ 📜analysis_options.yaml ┣ 📜my_app.iml ┣ 📜pubspec.lock ┗ 📜pubspec.yaml

24 @source: https://docs.flutter.dev/app-architecture/concepts https://docs.flutter.dev/app-architecture/case-study Common architecture concepts

25 @source: https://docs.flutter.dev/app-architecture/concepts https://docs.flutter.dev/app-architecture/case-study the Model-View-ViewModel design pattern (MVVM) app architecture

26 https://github.com/android/nowinandroid

27 @source: https://docs.flutter.dev/app-architecture/concepts https://docs.flutter.dev/app-architecture/case-study lib |____ui | |____core | | |____ui | | | |____ | | |____themes | |____ | | |____view_model | | | |_____.dart | | |____widgets | | | |_____screen.dart | | | |____ |____domain | |____models | | |____.dart |____data | |____repositories | | |____.dart | |____services | | |____.dart | |____model | | |____.dart |____config |____utils |____routing |____main_staging.dart |____main_development.dart |____main.dart

28 View View Model Repository Service API jsonplaceholder API https://news.ycombinator.com/ Model

29 ● freezed & generator ● riverpod & generator ● retrofit & generator ● dio

30 📦lib ┣ 📂domain ┃ ┗ 📂models ┃ ┃ ┣ 📂hacker_news ┃ ┃ ┃ ┣ 📜hn.dart ┃ ┃ ┃ ┣ 📜hn.freezed.dart ┃ ┃ ┃ ┗ 📜hn.g.dart ┃ ┃ ┗ 📂user ┃ ┃ ┃ ┣ 📜user.dart ┃ ┃ ┃ ┣ 📜user.freezed.dart ┃ ┃ ┃ ┗ 📜user.g.dart

31 📦lib ┣ 📂data ┃ ┣ 📂providers ┃ ┃ ┣ 📜dio_provider.dart ┃ ┃ ┗ 📜dio_provider.g.dart ┃ ┣ 📂repositories ┃ ┃ ┣ 📜hn_repository.dart ┃ ┃ ┣ 📜hn_repository.g.dart ┃ ┃ ┣ 📜user_repository.dart ┃ ┃ ┗ 📜user_repository.g.dart ┃ ┗ 📂services ┃ ┃ ┣ 📜hacker_news_api.dart ┃ ┃ ┣ 📜hacker_news_api.g.dart ┃ ┃ ┣ 📜user_api.dart ┃ ┃ ┗ 📜user_api.g.dart

32 📦lib ┣ 📂data ┃ ┣ 📂providers ┃ ┃ ┣ 📜dio_provider.dart ┃ ┃ ┗ 📜dio_provider.g.dart ┃ ┣ 📂repositories ┃ ┃ ┣ 📜hn_repository.dart ┃ ┃ ┣ 📜hn_repository.g.dart ┃ ┃ ┣ 📜user_repository.dart ┃ ┃ ┗ 📜user_repository.g.dart ┃ ┗ 📂services ┃ ┃ ┣ 📜hacker_news_api.dart ┃ ┃ ┣ 📜hacker_news_api.g.dart ┃ ┃ ┣ 📜user_api.dart ┃ ┃ ┗ 📜user_api.g.dart

33 📦lib ┣ 📂ui ┃ ┣ 📂core ┃ ┃ ┣ 📂shared ┃ ┃ ┗ 📜theme.dart ┃ ┣ 📂hacker_news ← Feature 1 ┃ ┃ ┣ 📂view_model ┃ ┃ ┃ ┣ 📜hacker_news_view_model.dart ┃ ┃ ┃ ┗ 📜hacker_news_view_model.g.dart ┃ ┃ ┗ 📂widgets ┃ ┃ ┃ ┣ 📜hacker_news_screen.dart ┃ ┃ ┃ ┗ 📜news_list_widget.dart ┃ ┣ 📂user ← Feature 2 ┃ ┃ ┣ 📂view_model ┃ ┃ ┃ ┣ 📜user_view_model.dart ┃ ┃ ┃ ┗ 📜user_view_model.g.dart ┃ ┃ ┗ 📂widgets ┃ ┃ ┃ ┣ 📜user_list_widget.dart ┃ ┃ ┃ ┗ 📜user_screen.dart

34 📦lib ┣ 📂ui ┃ ┣ 📂core ┃ ┃ ┣ 📂shared ┃ ┃ ┗ 📜theme.dart ┃ ┣ 📂hacker_news ← Feature 1 ┃ ┃ ┣ 📂view_model ┃ ┃ ┃ ┣ 📜hacker_news_view_model.dart ┃ ┃ ┃ ┗ 📜hacker_news_view_model.g.dart ┃ ┃ ┗ 📂widgets ┃ ┃ ┃ ┣ 📜hacker_news_screen.dart ┃ ┃ ┃ ┗ 📜news_list_widget.dart ┃ ┣ 📂user ← Feature 2 ┃ ┃ ┣ 📂view_model ┃ ┃ ┃ ┣ 📜user_view_model.dart ┃ ┃ ┃ ┗ 📜user_view_model.g.dart ┃ ┃ ┗ 📂widgets ┃ ┃ ┃ ┣ 📜user_list_widget.dart ┃ ┃ ┃ ┗ 📜user_screen.dart

35 Modularization https://github.com/android/nowinandroid

36 apps client_app data domain app package apps client_app repository service domain

37 apps client_app packages data domain apps client_app packages repository domain service app package

environment: sdk: ^3.6.0 38

39 root

40 root

41 domain

42 data

43 data

44 app

45 app

46

47 https://github.com/JAICHANGPARK/2025_flutter_in_production

Thank You 💙 @jaichangpark Flutter Seoul / GDG Golang Korea 박제창 48