gg_localize_refs 3.3.1

gg_localize_refs allows to switch a local package and its local checkouts to local pathes

gg_localize_refs

gg_localize_refs allows to switch a local package and its local checkouts to local pathes

Installation

dart pub global activate --source path .

How localization works

A package can reference its local sibling checkouts in one of three mutually exclusive modes. Exactly one is active at a time — switching modes always cleans up after the previous one.

Mode	Command	Where the refs live
local	change-refs-to-local	dependency_overrides in pubspec_overrides.yaml
git feature branch	change-refs-to-git-feature-branch --git-ref <ref>	git refs in pubspec.yaml
pub.dev	change-refs-to-pub-dev	version constraints in pubspec.yaml

For Dart packages, local mode does not modify pubspec.yaml: the published version constraints stay in place and the local paths go into pubspec_overrides.yaml, a file pub reads in addition to the manifest. That keeps a localized package publishable and keeps the local wiring in one file that a single command writes and removes again.

pubspec_overrides.yaml is committed. It contains only relative paths, so a shared ticket workspace resolves against the same sibling checkouts for everyone — and pub always excludes it from a published package. change-refs-to-local therefore removes a stale pubspec_overrides.yaml line from .gitignore if it finds one, because a file that is gitignored and checked in makes dart pub publish fail.

Leaving local mode removes the overrides this tool wrote — hand written entries in that file survive.

TypeScript/JavaScript projects have no equivalent file, so their link: specs are written into package.json as before.