fixes

Signed-off-by: flakey5 <[email protected]>

Author: flakey5

Makefile

@@ -389,7 +389,7 @@ test/addons/.docbuildstamp: $(DOCBUILDSTAMP_PREREQS) tools/doc/node_modules
 		echo "Skipping .docbuildstamp (no crypto and/or no ICU)"; \
 	else \
 		$(RM) -r test/addons/??_*/; \
-		$(call available-node, $(NPX) --prefix tools/doc api-docs-tooling generate -t addon-verify -i doc/api/addons.md -o test/addons/ --skip-lint) \
+		$(call available-node, $(NPX) --prefix tools/doc doc-kit generate -t addon-verify -i doc/api/addons.md -o test/addons/) \
 		[ $$? -eq 0 ] && touch $@; \
 	fi
 
@@ -829,12 +829,11 @@ out/doc/api: doc/api
 # For generating individual doc files instead of all at once
 out/doc/api/%.html out/doc/api/%.json: doc/api/%.md tools/doc/node_modules | out/doc/api
 	$(call available-node, \
-		$(NPX) --prefix tools/doc api-docs-tooling generate \
+		$(NPX) --prefix tools/doc doc-kit generate \
 		-t $(subst .,legacy-, $(suffix $@)) \
 		-i $< \
 		--ignore $(skip_apidoc_files) \
 		-o $(@D) \
-		--skip-lint \
 		-c ./CHANGELOG.md \
 		-v $(VERSION) \
 		--index doc/api/index.md \
@@ -1360,7 +1359,7 @@ lint-md: lint-js-doc lint-docs | tools/.mdlintstamp ## Lint the markdown documen
 .PHONY: lint-docs
 lint-docs: tools/doc/node_modules
 	$(info Running API Doc linter...)
-	$(call available-node, $(NPX) --prefix tools/doc api-docs-tooling lint -i doc/api/*.md)
+	$(call available-node, $(NPX) --prefix tools/doc doc-kit lint -i doc/api/*.md)
 
 run-format-md = tools/lint-md/lint-md.mjs --format $(LINT_MD_FILES)
 .PHONY: format-md

doc/contributing/api-documentation.md

@@ -1,7 +1,7 @@
 # Node.js API Documentation Tooling
 
 The Node.js API documentation is generated by an in-house tooling that resides
-in the [nodejs/api-docs-tooling](https://github.com/nodejs/api-docs-tooling)
+in the [nodejs/doc-kit](https://github.com/nodejs/doc-kit)
 repository.
 
 It is accessible in this repository from the `tools/doc` directory, where it is installed as an npm package.
@@ -30,8 +30,8 @@ nightlies or manual for releases) then moves the docs to
 
 **The key things to know about the tooling include:**
 
-1. It can be invoked via npx from the `tools/doc` directory (i.e. `npx --prefix tools/doc api-docs-tooling ...`)
-2. Its usage is detailed in the [nodejs/api-docs-tooling README](https://github.com/nodejs/api-docs-tooling/blob/main/README.md).
+1. It can be invoked via npx from the `tools/doc` directory (i.e. `npx --prefix tools/doc doc-kit ...`)
+2. Its usage is detailed in the [nodejs/doc-kit README](https://github.com/nodejs/doc-kit/blob/main/README.md).
 3. The tooling can process multiple files at a time.
 4. The tooling uses a set of dependencies as described in the dependencies
    section.
@@ -73,7 +73,7 @@ meant to be a guide on how to write documentation for Node.js.
 
 ```bash
 # cd tools/doc
-npx api-docs-tooling
+npx doc-kit
 ```
 
 **OR**
@@ -173,7 +173,7 @@ added: v0.10.0
 
 * Returns: {SomeClass | null} The next `SomeClass` in line.
 
-`SomeClass` must be registered in `https://github.com/nodejs/api-docs-tooling/blob/main/src/constants.mjs` to be properly parsed in `{type}` fields.
+`SomeClass` must be registered in `https://github.com/nodejs/doc-kit/blob/main/src/constants.mjs` to be properly parsed in `{type}` fields.
 
 ### `SomeClass.someProperty`
 

doc/contributing/maintaining/maintaining-types-for-nodejs.md

@@ -97,7 +97,7 @@ As part of the regular build/release process both the `html` and
 `json` files are published to [nodejs.org][].
 
 The generator that does the conversion is in the
-[nodejs/api-docs-tooling][]
+[nodejs/doc-kit][]
 repository.
 
 ## Markdown structure
@@ -124,5 +124,5 @@ JSON output.
 [documentation-style-guide]: https://github.com/nodejs/node/blob/HEAD/doc/README.md#documentation-style-guide
 [next-10]: https://github.com/nodejs/next-10/blob/HEAD/meetings/summit-nov-2021.md#suitable-types-for-end-users
 [nodejs.org]: https://nodejs.org/en/docs/
-[nodejs/api-docs-tooling]: https://github.com/nodejs/api-docs-tooling
+[nodejs/doc-kit]: https://github.com/nodejs/doc-kit
 [suitable types for end-users]: https://github.com/nodejs/node/blob/HEAD/doc/contributing/technical-priorities.md#suitable-types-for-end-users

test/doctool/test-apilinks.mjs

@@ -26,7 +26,7 @@ fs.readdirSync(apilinks).forEach((fixture) => {
     [
       '--prefix',
       docToolingDir,
-      'api-docs-tooling',
+      'doc-kit',
       'generate',
       '-t',
       'api-links',
@@ -45,7 +45,7 @@ fs.readdirSync(apilinks).forEach((fixture) => {
   for (const [k, v] of Object.entries(expectedLinks)) {
     assert.ok(k in actualLinks, `link not found: ${k}`);
     assert.ok(actualLinks[k].endsWith('/' + v),
-              `link ${actualLinks[k]} expected to end with ${v}`);
+      `link ${actualLinks[k]} expected to end with ${v}`);
     delete actualLinks[k];
   }
 

tools/doc/README.md

@@ -1,4 +1,4 @@
 # Documentation Tooling
 
-The Node.js API documentation tooling lives in [nodejs/api-docs-tooling](https://github.com/nodejs/api-docs-tooling).
+The Node.js API documentation tooling lives in [nodejs/doc-kit](https://github.com/nodejs/doc-kit).
 This module exists just to make it usable in Node.js core, any changes to the tooling should be done in that repository.

tools/doc/get-latest-commit.mjs

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 
-const res = await fetch('https://api.github.com/repos/nodejs/api-docs-tooling/commits/main', {
+const res = await fetch('https://api.github.com/repos/nodejs/doc-kit/commits/main', {
   headers: {
     accept: 'application/vnd.github.VERSION.sha',
   },