Skip to content

resilix.js.org - #12312

Open
lintdeveloper wants to merge 2 commits into
js-org:masterfrom
lintdeveloper:add-resilix
Open

resilix.js.org#12312
lintdeveloper wants to merge 2 commits into
js-org:masterfrom
lintdeveloper:add-resilix

Conversation

@lintdeveloper

Copy link
Copy Markdown

The site content is the documentation for resilix, an open-source JavaScript resilience library — circuit breaking, adaptive concurrency limiting, retries with budgets, and hedging — and is relevant to JavaScript developers specifically because it documents a JavaScript/TypeScript npm package and the failure-handling problems it addresses in JavaScript services.

The site is an eighteen-page guide: getting started, a page per policy, the design decisions behind the library, and three design specs. Source repository: https://github.com/lintdeveloper/resilix

A note on why the library exists, since the content requirement asks what makes it relevant to this community specifically: JavaScript has plenty of fault-handling libraries, but its load limiting is effectively locked inside two RPC clients — hedging and retry budgets only in @grpc/grpc-js, adaptive throttling only in the AWS SDK — and is unavailable to anyone calling a plain HTTP API, a database or a queue. resilix implements those patterns as a zero-dependency package with no I/O, so they work anywhere JavaScript runs (Node, Bun, Deno and Cloudflare Workers, each exercised in CI).

The subdomain requested matches the repository name, per Subdomain Determination for a project page at lintdeveloper.github.io/resilix.

One sequencing note: the site is published by a GitHub Actions workflow, so a CNAME file in the artifact is not processed and the custom domain has to be set in the repository settings — which immediately redirects the github.io URL above. I have deliberately not set it yet so that the content stays reachable for review, and will set it as soon as this is approved or merged. Happy to set it beforehand if you would rather verify that way.

@github-actions github-actions Bot changed the title Add resilix.js.org resilix.js.org Aug 16, 2026
@github-actions

Copy link
Copy Markdown

✅ All validations passed! Please wait for the JS.org maintainers to process your subdomain request.

lintdeveloper added a commit to lintdeveloper/resilix that referenced this pull request Aug 16, 2026
resilix.github.io cannot be had. That hostname derives from a GitHub ACCOUNT
name, not a repo name, and github.com/Resilix is already taken — a dormant
account created Aug 2023 with no repos and no activity since. GitHub does not
release inactive usernames, so no amount of repo-side configuration reaches it.

js-org/js.org#12312 requests resilix.js.org instead: free, unclaimed, and the
subdomain matches the repo name exactly, which is what their subdomain rules
require for a project page. Their validation bot passed both checks.

Nothing is switched over yet, on purpose. Publishing via a workflow means an
artifact CNAME file is ignored and the domain must be set on the Pages config
— and the moment it is, the github.io URL 301s to a hostname that will not
resolve until they merge. Their most common rejection is a reviewer finding no
content on the page, so the site stays reachable until it is approved.

docs/DEPLOYING.md carries the cutover sequence, the reason for the ordering,
and the verification commands, so this is not a fact living only in a PR
thread. It is excluded from the published site — repo operations are not user
documentation.

Also recorded there: js.org is a free subdomain, not ownership. Their
naming-conflict policy breaks ties on stars after a three-month grace period.
resilix.dev is unregistered and is the only route that actually locks it down.

@MattIPv4 MattIPv4 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Commit valid, site appears to have content *

* based off https://github.com/lintdeveloper/resilix/tree/main/docs

@MattIPv4

Copy link
Copy Markdown
Member

FYI, before we can accept your domain request, you need to configure your GitHub Pages site to use the requested js.org subdomain. Head to your repository settings, locate the Pages settings (under Code and Automation), and enter the js.org subdomain in the custom domain field. 📝

@MattIPv4 MattIPv4 added add This PR/issue is regarding adding a new subdomain user This PR/issue is regarding a target on a GitHub user account project This PR has a target of a project on an organisation or user account awaiting custom domain This PR is waiting for the GitHub Pages target to set the custom domain labels Aug 16, 2026
@indus

indus commented Aug 18, 2026

Copy link
Copy Markdown
Member

@lintdeveloper any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

add This PR/issue is regarding adding a new subdomain awaiting custom domain This PR is waiting for the GitHub Pages target to set the custom domain project This PR has a target of a project on an organisation or user account user This PR/issue is regarding a target on a GitHub user account

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants