Practise the standard verbs for publishing npm packages reliably.
0 / 5 completed
1 / 5
Fill in: 'We ___ a package version bump before publishing, rather than pushing a release nobody's actually incremented correctly.'
We 'run a version bump' — the standard, simple collocation for updating a package's version before release. The other options are less idiomatic here.
2 / 5
Fill in: 'Publishing without running the build step first can ___ consumers installing a package with source nobody's actually compiled.'
We say a skipped build will 'leave' consumers with uncompiled source — the standard, natural collocation for the resulting breakage. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a changelog entry for every published version, rather than a release nobody can actually tell what's different in.'
We 'write a changelog entry' — the standard, simple collocation for documenting what changed in a published package. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every published package against a clean install in a scratch folder, rather than trusting a build nobody's actually verified works.'
We 'test a package' — the standard, simple collocation for validating a published release before announcing it. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a broken publish immediately with npm deprecate, rather than leaving a bad version live that nobody's actually warned users off.'
We 'flag a publish' — the standard, simple collocation for marking a bad package version as deprecated. The other options aren't idiomatic here.