Feat/nextjs migration - #2
Merged
Merged
Conversation
The card was a title, a description and a line of metadata. It now carries the icon and version, the keywords the package ships with, its last three releases with their bump badges and dates, and links to the changelog and to npm. All of it comes from npm and from the package's own changelog, so the card says what is published rather than what someone remembered to write down. No features list: there is none in the data, and inventing one would be worse than leaving it out. An article rather than one big link, since the card now has several of its own and a link inside a link is invalid. The title carries an ::after overlay so the whole card stays clickable, with the other two raised above it. Bump badges reuse BUMP_STYLES, so a patch cannot be one colour here and another on the changelog.
The repo's writing rules rule them out, and the fix is to change the sentence rather than swap the dash for a comma, so all three are rewritten.
The landing page's header deliberately has none and the docs pages have no top bar at all, so fumadocs' navbar on the blog was the only header on the site with one under it. The colour goes rather than the border, so nothing moves by the pixel the border occupies.
The title bar is gone and the panel is a frame with padding rather than a bordered box: a wider radius, a light rim, and the content sitting inside it as its own inset card. The card is lighter than the chrome around it, which is the part that actually does the work. In dark mode the two swap, since a dark window has the lighter chrome and the darker content. The sidebar sits on the frame itself, the way a mac sidebar belongs to the window rather than being a panel inside it, so its divider goes and the gap to the content card is the separation.
CI checks out this repository alone, so the local monorepo path never resolves there and every changelog came from raw.githubusercontent at axonpack/axonpack main. That tied this build to another repository's branch state: react-pretty-print is on npm but its source has never reached that main, so the fetch 404s, the throw is uncaught, and the next deploy would have failed. So would every nightly cron after it. The changelog comes from the package's own npm tarball now, read with a small tar walk rather than a dependency. A published package cannot 404 its own tarball, because the tarball is what was published. It is also what the README always said this site does. An unreadable changelog no longer fails the build either. It warns and leaves the committed page alone, since a deploy should not die because npm blipped. Verified by rebuilding the directory layout with no monorepo above it, which is CI's situation exactly: both packages read from the tarball, exit 0, and the three generated files came out byte-identical to the local-checkout run.
Each pane now draws what its tab actually renders: a JSON tree, charts with axes, a stack listing. The sample data moved to devtools-panes.ts so the drawing and the content are separate files. Drops the Debug pane, so the carousel is five panes over 20s and the keyframes are recut to match.
Read from the GitHub API at build time, next to the download counts, so the page stays static. A rate limit or an outage hides the number instead of failing the build.
`next dev` writes AGENTS.md and re-adds it if it is deleted, so tracking it is the only way the tree stays clean.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.