1.28.2 - Taxonomy fields suggest something before you type

Clicking a field in the Consolidated Taxonomy Panel before typing anything opened a dropdown with nothing in it, so an editor had to guess at a term name before the field would show them anything. It now lists the whole taxonomy on that first click, most-used terms first. The release zip also drops about a megabyte of npm lockfiles that were never used at runtime.

• [BUG FIX] A taxonomy chip field with nothing typed into it now lists the taxonomy's terms, ordered by how many posts already use them. Previously the field fetched no terms until something was typed, so the only terms it knew about were the ones already assigned — and those are exactly what a suggestion list leaves out, which is why the dropdown came up empty.
• [CHANGE] The release zip no longer contains package.json or any package-lock.json — roughly 1 MB uncompressed that no site ever read. Nothing in the plugin loads them at runtime, and every build script reads the repository's copy rather than the packaged one. composer.json and composer.lock stay, since they are genuinely useful for pinning down a dependency version during an incident.

Unused terms are still there

They sort to the end, with a count of zero, rather than being hidden — a term nobody has used yet still has to be assignable. Typing switches the list from most-used to a search, as before.

The list is capped at the hundred most-used terms. On a taxonomy larger than that, typing searches the rest.