Skip to content

build: allow linting node.1#64157

Open
avivkeller wants to merge 1 commit into
nodejs:mainfrom
avivkeller:lint-node1
Open

build: allow linting node.1#64157
avivkeller wants to merge 1 commit into
nodejs:mainfrom
avivkeller:lint-node1

Conversation

@avivkeller

@avivkeller avivkeller commented Jun 26, 2026

Copy link
Copy Markdown
Member

Adds make doc/node.1 without triggering it on normal builds

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. needs-ci PRs that need a full CI run. labels Jun 26, 2026
Comment thread Makefile
Signed-off-by: avivkeller <me@aviv.sh>

@aduh95 aduh95 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Wait, it looks like it needs internet access, which is a problem for integrators who run the tests in a sandbox, and also completely irrelevant for node.1:

UNDICI 59249: connecting to raw.githubusercontent.com using https:undefined
UNDICI 59249: connecting to raw.githubusercontent.com using https:undefined
UNDICI 59249: connection to raw.githubusercontent.com using https:undefined errored - No such binding: crypto
UNDICI 59249: connection to raw.githubusercontent.com using https:undefined errored - No such binding: crypto
UNDICI 59249: request to GET https://raw.githubusercontent.com/nodejs/node/HEAD/CHANGELOG.md errored - No such binding: crypto
UNDICI 59249: request to GET https://raw.githubusercontent.com//nodejs/node/HEAD/CHANGELOG.md errored - No such binding: crypto
[08:04:00.088] ERROR: fetch failed

I got rid of it by commenting out the following in tools/doc/node_modules/@node-core/doc-kit/src/utils/configuration/index.mjs:

        changelog: populate(CHANGELOG_URL, {
          repository: 'nodejs/node',
          ref: 'HEAD',
        }),

@aduh95

aduh95 commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Another problem I've seen is that if I update node.1 manually, it's going to tell me doc/node.1 is out of date; run `make doc/node.1` to regenerate it. However, trying to run it:

$ make doc/node.1 
make: 'doc/node.1' is up to date.

Should we recommend rm doc/node.1 && make doc/node.1?

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

Labels

build Issues and PRs related to build files or the CI. needs-ci PRs that need a full CI run.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants