treesitter: parsers -> grammarPlugins

[HeitorAugustoLN]

For compatibility with 25.11, as reported by: #1312 (comment)

Sanity Checking

• I have updated the changelog as per my changes
• I have tested, and self-reviewed my code
• My changes fit guidelines found in hacking nvf
• Style and consistency
  • I ran Alejandra to format my code (nix fmt)
  • My code conforms to the editorconfig configuration of the project
  • My changes are consistent with the rest of the codebase
• If new changes are particularly complex:
  • My code includes comments in particularly complex areas
  • I have added a section in the manual
  • (For breaking changes) I have included a migration guide
• Package(s) built:
  • .#nix (default package)
  • .#maximal
  • .#docs-html (manual, must build)
  • .#docs-linkcheck (optional, please build if adding links)
• Tested on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin

---

Add a 👍 reaction to pull requests you find important.

[github-actions]

🚀 Live preview deployed from 3178774

View it here:

Debug Information

Triggered by: HeitorAugustoLN

HEAD at: parsers-to-grammarPlugins

Reruns: 1832

[NotAShelf]

As a non-blocking question, is there a reason we're avoiding builtGrammars? I couldn't find anything on this in the PR but I'll admit that I haven't checked too carefully.

[HeitorAugustoLN]

is there a reason we're avoiding builtGrammars?

I have explained it here: #1315 (comment)

[NotAShelf]

Got it, thanks.