fix(docs): Noir LSP and binaries installed by the aztec installer - #22675
Merged
Merged
Conversation
critesjosh
approved these changes
Apr 21, 2026
vezenovm
force-pushed
the
docs/nargo-lsp-path
branch
from
April 21, 2026 14:09
991688d to
238949b
Compare
vezenovm
enabled auto-merge
April 21, 2026 14:09
vezenovm
added this pull request to the merge queue
Apr 21, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Apr 21, 2026
vezenovm
added this pull request to the merge queue
Apr 21, 2026
AztecBot
pushed a commit
that referenced
this pull request
Apr 21, 2026
…2675) ## Summary Stop conflating `aztec` with `nargo` in the Noir LSP setup guide, and list every binary the installer actually provides. The docs led me down the wrong path while trying to get the LSP working when going through the counter contract tutorial. - `docs/aztec-nr/installation.md`: rewritten around `nargo` only. Drops the old `which aztec` guidance (which pointed users at `$HOME/.aztec/current/node_modules/.bin/aztec`, unusable as an LSP backend). Recommends leaving `Noir: Nargo Path` empty for auto-discovery; falls back to `which nargo`. Adds troubleshooting for `startFailed` and shadowed `nargo` on `PATH`. - `getting_started_on_local_network.md`: install list now matches the `aztec-install` output (adds `nargo`, `noir-profiler`, `bb`) and links to the Noir VSCode Extension guide.
Collaborator
|
✅ Successfully backported to backport-to-v4-next-staging #22699. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stop conflating
aztecwithnargoin the Noir LSP setup guide, and list every binary the installer actually provides.The docs led me down the wrong path while trying to get the LSP working when going through the counter contract tutorial.
docs/aztec-nr/installation.md: rewritten aroundnargoonly. Drops the oldwhich aztecguidance (which pointed users at$HOME/.aztec/current/node_modules/.bin/aztec, unusable as an LSP backend). Recommends leavingNoir: Nargo Pathempty for auto-discovery; falls back towhich nargo. Adds troubleshooting forstartFailedand shadowednargoonPATH.getting_started_on_local_network.md: install list now matches theaztec-installoutput (addsnargo,noir-profiler,bb) and links to the Noir VSCode Extension guide.