Skip to content

doc: fix broken using link in ffi.md - #65632

Open
soulee-dev wants to merge 1 commit into
nodejs:mainfrom
soulee-dev:doc-fix-ffi-using-link
Open

doc: fix broken using link in ffi.md#65632
soulee-dev wants to merge 1 commit into
nodejs:mainfrom
soulee-dev:doc-fix-ffi-using-link

Conversation

@soulee-dev

Copy link
Copy Markdown
Contributor

The [using] link in ffi.md points at
proposal-explicit-resource-management/#sec-using-declarations, but that
fragment does not exist, so the link silently resolves to the top of the page.

Point it at the MDN page for using, which fs.md already uses for the same
reference.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/ffi

@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to Node.js documentation. ffi Issues and PRs related to experimental Foreign Function Interface support. labels Aug 29, 2026
@daeyeon

daeyeon commented Aug 29, 2026

Copy link
Copy Markdown
Member

Can you rebase onto the latest main? #65636 fixed the CI failures.

The `#sec-using-declarations` fragment does not exist in the explicit
resource management proposal, so the link silently resolves to the top
of the page. The proposal defines `using` under
`#sec-let-and-const-declarations`, and the only `using`-related section
ids are static semantics entries.

Point the reference at the MDN page for `using` instead, matching the
`[`using`]` definition already used in fs.md.

Signed-off-by: Soul Lee <alus20x@gmail.com>
@soulee-dev
soulee-dev force-pushed the doc-fix-ffi-using-link branch from 8249db8 to 6fa9f1a Compare August 29, 2026 13:40
@soulee-dev

soulee-dev commented Aug 29, 2026

Copy link
Copy Markdown
Contributor Author

@daeyeon Rebased onto the latest main (452c8c5), which includes #65636.
No changes other than the rebase.

Thanks for the heads-up!

@trivikr

trivikr commented Aug 29, 2026

Copy link
Copy Markdown
Member

#65636 fixed the CI failures

The #65636 enables node:ffi by default, and is not fixing CI failures.

If you meant #65629, it fixed CI failures in AIX on Jenkins CI.
A doc change this one doesn't run Jenkins CI, and wouldn't need a rebase.

@daeyeon

daeyeon commented Aug 29, 2026

Copy link
Copy Markdown
Member

The #65636 enables node:ffi by default, and is not fixing CI failures.

#65636 did not enable node:ffi; #65475 did. #65636 updated the test and fixed the CI failure on main.
This PR was based on main before that fix, resulting in CI failures in GHA.

@daeyeon daeyeon added the author ready PRs with CI started, the required approvals, and no outstanding review comments. label Aug 29, 2026
@trivikr

trivikr commented Aug 29, 2026

Copy link
Copy Markdown
Member

#65636 did not enable node:ffi; #65475 did.

My bad. You're right. There were two different CI fixes.

@trivikr trivikr added the commit-queue PRs queued for automated landing through the Commit Queue. label Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs with CI started, the required approvals, and no outstanding review comments. commit-queue PRs queued for automated landing through the Commit Queue. doc Issues and PRs related to Node.js documentation. ffi Issues and PRs related to experimental Foreign Function Interface support.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants