Skip to content
Install Plugin >

Symptoms:

  • No code completion suggestions
  • No error highlighting
  • No hover information
  • Status bar doesn’t show “Noir” indicator

Solutions:

  1. Verify nargo is installed

    Terminal window
    nargo --version

    If not found, see Installation for setup.

  2. Check PATH configuration Your IDE might not inherit your shell’s PATH. Try:

    • Launch IDE from terminal: open -a "IntelliJ IDEA"
    • Or set explicit path in Settings → Languages & Frameworks → Noir
  3. Check LSP is enabled Go to Settings → Languages & Frameworks → Noir and ensure “Enable LSP” is checked.

  4. Restart the language server Tools → Noir → Restart Language Server

  5. Restart the IDE Sometimes a full restart is needed after configuration changes.

Symptoms:

  • .nr files show as plain text
  • Keywords aren’t colored
  • No bracket matching

Solutions:

  1. Check file extension Ensure the file ends with .nr (not .noir or other variants).

  2. Verify plugin is enabled Go to Settings → Plugins and ensure “Noir” is listed and has a checkmark.

  3. Reopen the file Close the file and reopen it. Sometimes the file type isn’t recognized immediately.

  4. Clear caches File → Invalidate Caches → Invalidate and Restart

Symptoms:

  • Error message: “nargo not found”
  • LSP fails to start
  • Actions like “Expand Macros” fail

Solutions:

nargo is typically installed to ~/.nargo/bin. Ensure this is in your PATH:

For Zsh (macOS default):

Terminal window
# Add to ~/.zshrc
export PATH="$HOME/.nargo/bin:$PATH"

For Bash:

Terminal window
# Add to ~/.bashrc or ~/.bash_profile
export PATH="$HOME/.nargo/bin:$PATH"

After editing, restart your terminal and IDE.

IDEs launched from Dock/Spotlight may not inherit shell PATH. Options:

  1. Launch from terminal:

    Terminal window
    open -a "IntelliJ IDEA"
    # or
    open -a "RustRover"
  2. Set explicit path: Settings → Languages & Frameworks → Noir → Nargo path

    /Users/yourname/.nargo/bin/nargo
  3. Fix system PATH (macOS):

    Terminal window
    sudo launchctl config user path "$HOME/.nargo/bin:/usr/local/bin:/usr/bin:/bin"

    Then restart your Mac.

Symptoms:

  • Features work briefly then stop
  • Repeated “LSP server stopped” notifications
  • Errors in IDE logs

Solutions:

  1. Check IDE logs Help → Show Log in Finder/Explorer Search for “Noir” or “nargo” to find error messages.

  2. Update nargo

    Terminal window
    noirup

    Older nargo versions may have LSP bugs.

  3. Try a different project If it only crashes on one project, there may be a syntax issue in your code that crashes the LSP.

  4. Check for conflicting plugins Disable other language plugins temporarily to check for conflicts.

Symptoms:

  • Long delay before completion popup appears
  • IDE becomes unresponsive when typing
  • High CPU usage

Solutions:

  1. Enable lightweight mode Settings → Languages & Frameworks → Noir → Enable “Lightweight mode”

    This disables completion while keeping diagnostics and navigation.

  2. Check project size Large projects with many files can slow down LSP. Consider:

    • Excluding non-essential directories
    • Breaking into smaller sub-projects
  3. Update nargo

    Terminal window
    noirup

    Newer versions may have performance improvements.

  4. Increase IDE memory Help → Edit Custom VM Options

    -Xmx4096m

    Restart IDE after changing.

Symptoms:

  • Errors aren’t highlighted
  • No problems in Problems tool window
  • Code compiles with errors but IDE shows none

Solutions:

  1. Wait for indexing After opening a project, LSP needs time to analyze files. Wait for indexing to complete (shown in status bar).

  2. Check for nargo compile errors Run nargo check in terminal. If it fails with an error, LSP may not be able to start properly.

  3. Restart LSP Tools → Noir → Restart Language Server

  4. Check lightweight mode Lightweight mode still shows diagnostics. If diagnostics are missing, it’s not a lightweight mode issue.

To find detailed error information:

  1. Go to Help → Show Log in Finder/Explorer

  2. Open idea.log (or the latest log file)

  3. Search for:

    • “Noir”
    • “nargo”
    • “LSP”
    • “Error”
  4. Look for stack traces or error messages

Common log locations:

OSLocation
macOS~/Library/Logs/JetBrains/[IDE]/idea.log
Windows%APPDATA%\JetBrains\[IDE]\log\idea.log
Linux~/.cache/JetBrains/[IDE]/log/idea.log

If these solutions don’t work:

  1. Check GitHub Issues View existing issues

  2. Open a new issue Include:

    • IDE name and version
    • Plugin version
    • nargo version (nargo --version)
    • Steps to reproduce
    • Relevant log excerpts
  3. Noir Community