Skip to content

Documented that pub workspaces can be nested #7175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SoufianElfouzari wants to merge 3 commits into
base: main
Choose a base branch
from
+8 −1
Open

Documented that pub workspaces can be nested #7175

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f05b252
Improved: Documented that pub workspaces can be nested
SoufianElfouzari Feb 16, 2026
c951073
rephrase the pub worspace nested section
SoufianElfouzari Feb 16, 2026
b5bdd42
Merge branch 'main' into mention-nested-workspaces
conooi Feb 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion src/content/tools/pub/workspaces.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,14 @@ There are some downsides to this setup:
separate analysis contexts for each package, increasing memory usage.

Pub allows you to organize your repository as a _workspace_ using a single
shared resolution for all your packages.
shared resolution for all your packages.

Pub workspaces can also be nested. A package that is part of a workspace can
define its own workspace by including a `workspace` section in its
`pubspec.yaml` file. This allows hierarchical organization of large repositories,
where a workspace can contain packages that themselves manage additional packages
as a separate workspace.

Using workspaces for large repositories reduces the amount of memory
required for analysis, hence improving performance.

Expand Down