docs(readme): note what the install specifier costs per repaint - #570
Merged
Merged
Conversation
The status line command runs once per repaint, so its invocation cost is paid continuously, but nothing in the README said so or gave a number. Record the measurement. Under Bun the specifier decides it: bunx re-resolves the latest dist-tag against the registry every run, since a dist-tag is not cacheable, and dropping @latest is worth about 430 ms per repaint. Scope the claim to Bun, because npx measured 1082 ms on @latest against 1135 ms pinned, so pinning buys nothing there.
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
2 participants
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.
The status line command runs once per repaint, so its invocation cost is paid continuously. The README
lists the command forms without saying what they cost, and the form the installer writes is the most
expensive one under Bun.
Windows, warm cache, median of five
--versionruns (exits before rendering):bunx -y ccstatusline@latestbunx -y ccstatusline@2.2.27bunx -y ccstatuslinenpx -y ccstatusline@latestnpx -y ccstatusline@2.2.27bunxre-resolves thelatestdist-tag every run, since a dist-tag is not cacheable; it rewrites itstemp
package.jsoneach time, and withBUN_CONFIG_REGISTRYon a closed port any version specifierfails with
ConnectionRefused downloading package manifestwhile the bare specifier runs offline.Scoped to Bun deliberately:
npxpinned measured marginally slower, so this is Bun's resolutionbehavior, not the dist-tag. Docs only. Single Windows host, and the note says so.