Skip to content

Regenerate llms-full references#4738

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/update-llms-full
Open

Regenerate llms-full references#4738
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/update-llms-full

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Regenerates the machine-readable docs reference files from the current docs source.
Source-doc changes may land before this generated-reference PR is merged; merge this PR to refresh the hosted llms-full endpoints.

Validation performed by this workflow:

  • bash script/generate-llms-full-test.bash
  • node script/generate-llms-full.mjs

Expected generated PR checks:

  • ci-required / required-pr-gate
  • Validate llms-full.txt / check-llms-full

@greptile-apps

greptile-apps Bot commented Jul 18, 2026

Copy link
Copy Markdown

Greptile Summary

This PR refreshes the generated Node renderer documentation. The main changes are:

  • Raises the default setup guidance from Node.js 18+ to Node.js 20+.
  • Adds Fastify 5 compatibility details and Fastify 4 override links.

Confidence Score: 5/5

This looks mergeable after correcting the Node.js 18 startup description.

  • The generated content matches its source documentation.
  • The package versions and engine floor match the new guidance.
  • The statement that the renderer exits is stronger than the explicit runtime version check.

llms-full.txt

Important Files Changed

Filename Overview
llms-full.txt Updates generated Node.js and Fastify compatibility guidance, but overstates the renderer’s explicit startup behavior on Node.js 18.

Reviews (1): Last reviewed commit: "Regenerate llms-full references" | Re-trigger Greptile

Comment thread llms-full.txt
cd renderer-app
```
2. Make sure you have **Node.js 18+** and a JavaScript package manager such as **npm**, **pnpm**, **Yarn**, or **bun**.
2. Make sure you have **Node.js 20+** and a JavaScript package manager such as **npm**, **pnpm**, **Yarn**, or **bun**. The default setup bundles Fastify 5, which requires Node.js 20+ — on Node.js 18 the renderer exits at startup unless you pin Fastify 4 via your package manager's dependency-override mechanism (npm [`overrides`](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#overrides), Yarn/Bun [`resolutions`](https://yarnpkg.com/configuration/manifest#resolutions), or pnpm [`pnpm.overrides`](https://pnpm.io/package_json#pnpmoverrides)). (The package's `engines.node` floor is `>=18.19.0`, which applies only to that Fastify 4 path.)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Startup Exit Is Overstated

The renderer’s Node.js 18 and Fastify 5 version check only emits a warning; it does not exit or throw. If Fastify still initializes on a given Node.js 18 release, this reference incorrectly states that the renderer always exits and can lead users to apply an unnecessary dependency override.

Context Used: CLAUDE.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@github-actions
github-actions Bot force-pushed the docs/update-llms-full branch from 0c409d6 to c582347 Compare July 18, 2026 05:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants