You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three things, all of them stale rather than newly broken.
**The README listed seven of the ten packages.** `dastdown`,
`slate-utils` and `generic-html-renderer` were never added when they
appeared, so the monorepo's own front page under-reported itself by
three. (`to-markdown` was already there.)
**Every link pointed at a `master` branch this repository does not
have.** The default branch is `main`; `master` resolves only because
GitHub still redirects the old default branch name, which is not
something to keep depending on. 10 links in the README and the
`homepage` of all ten manifests.
**Two of those homepages were a genuine 404**, redirect or not:
`datocms-structured-text-utils` pointed at `packages/datocms-structured-text-utils`
and `datocms-structured-text-slate-utils` at
`packages/datocms-structured-text-slate-utils`, neither of which exists —
the directories are `packages/utils` and `packages/slate-utils`. `homepage`
is what npm renders on a package's page, so those were dead links on two
published packages, one of them the most depended-on in the repo.
Verified: all ten now return HTTP 200 directly, with no redirect.
Also deletes `packages/to-markdown/REVIEW.md`, 2787 lines of one-off
review notes committed by accident alongside the package itself. It is
dated 2025-10-01, reviews version 5.1.4, and its headline is "Block
release until P0 items are fixed" — for a package that has since been
released and is now at 6.0.0. Checked before deleting that the P0 it
blocks on is gone: it warned that `render()` kept list state at module
level and was therefore unsafe under `Promise.all`. There is no
module-scope mutable state in the source any more, and rendering three
documents concurrently now produces output identical to rendering them
in sequence. The file is not in `files`, so it was never published.
No changeset: nothing here changes behaviour, and the manifest links
reach npm with each package's next release.
0 commit comments