Repository navigation
Publish as @runonflux/insight-ui 2.0.0 - #21
Merged
MorningLightMountain713 merged 5 commits intoOct 28, 2026
Merged
MorningLightMountain713 merged 5 commits into
MorningLightMountain713 merged 5 commits into
Conversation
The explorer's React application is published to npm under the runonflux scope. The package ships the bitcore-node service and the built site in public/; bitcore-node runs it as the service insight-ui. The README installs it and points development at frontend/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The explorer is the React application in frontend/, built into public/. Gruntfile.js, bower.json, .bowerrc, .jshintrc, the po/ translations, the root yarn.lock of grunt's packages, .npmignore and the AngularJS lines in .gitignore belonged to the AngularJS build. The frontend names its repository by https. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CI runs the tests on every push and pull request. A published GitHub release sets the package version from its tag, runs the tests and stages that version on npm through trusted publishing: it stays unpublished until a maintainer approves it on npmjs.com with 2FA. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
npm verifies a provenance-signed publish by comparing repository.url with the GitHub repository the workflow ran in, case-sensitively. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The list only collected live transactions, so it sat empty until the explorer's mempool saw a new one. It now starts from the newest block's transactions, refetched on each new block, with live ones above them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Publishes
@runonflux/insight-ui2.0.0: the bitcore-node service and the built React site inpublic/. bitcore-node runs it as the serviceinsight-ui. Removes the AngularJS application's build files (Gruntfile, bower, po/, the grunt-era yarn.lock). CI runs the frontend's type check, lint and format check and requirespublic/to be exactly whatfrontend/builds.Stacked on #20 (the home page cards fix).
Running on labnet (the lab's own Flux chain): the API answers identically to 1.3.0, the React UI works against it in a browser, live updates arrive over the websocket, and a transaction sent through
/api/tx/sendwas mined.Publishing. This package is released through npm's staged publishing. Publishing a
GitHub release (tag
vX.Y.Z) runs CI, which sets the version from the tag, runs the tests andstages that version on npm through trusted publishing (GitHub's OIDC; no npm token is stored).
A staged version is not public: nobody can install it until a maintainer approves it on
npmjs.com, or with
npm stage approve, which requires 2FA. Each package needs a trustedpublisher on npmjs.com for this repository's
ci.yml, allowing staged publishing only.Order: each layer is published before the one above it. The packages depend on each other
by version, so they are released lowest first, each approved before the next:
bitcoind-rpcandbitcore-libbitcore-messagebitcore-node,insight-apiandinsight-uiUntil the packages below this one are on npm, this PR's CI cannot install them and fails; that
is the order, not a broken change. Once they are published, this PR refreshes its
package-lock.jsonagainst npm in one commit, and CI passes.🤖 Generated with Claude Code