Practise the standard verbs for configuring a monorepo workspace cleanly.
0 / 5 completed
1 / 5
Fill in: 'We ___ shared workspace config at the monorepo root, rather than duplicating the same settings in every actual package.'
We 'centralize config' — the standard, simple collocation for consolidating shared settings in a monorepo. The other options are less idiomatic here.
2 / 5
Fill in: 'An unpinned dependency version at the workspace root can ___ every package resolving a slightly different build nobody actually expects.'
We say an unpinned version will 'leave' packages resolving inconsistently — the standard, natural collocation for the resulting drift. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ package boundaries explicitly in the workspace manifest, rather than an import path nobody's actually restricted.'
We 'declare boundaries' — the standard, simple collocation for defining which packages can depend on which. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every workspace script against a clean checkout, rather than trusting a config nobody's actually run from scratch.'
We 'test a script' — the standard, simple collocation for validating workspace tooling from a fresh clone. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ workspace dependency graphs periodically for cycles, rather than discovering a circular import only once the build's actually broken.'
We 'audit a graph' — the standard, simple collocation for reviewing monorepo dependency structure. The other options aren't idiomatic here.