Troubleshooting

This guide covers common issues you might encounter while using Pacy and their solutions.

Installation Issues

IDE Extension Installation Issues

Installation from the command line might not work for some users. Here, we provide 2 more alternative ways to install the extension.

Install from a link

You can install the extension to VSCode from the following link:

• Install VSCode Extension
• Install Cursor Extension
• Install Windsurf Extension

For Cursor and Windsurf, you can download the following file and drag and drop it to your editor’s extensions tab:

• Pacy Devtools Bridge

Manual Installation

If these links don’t work, or you’d like to use pacy with another VSCode-based editor, you can search “Pacy Devtools Bridge” in your editor, or you can download the .vsix file from the following link, and later drag and drop it into your editor’s extensions tab:

• Pacy Devtools Bridge in VSCode Marketplace

Hint

A VS Code extension’s offline install package (VSIX) is available at:

https://${publisher}.gallery.vsassets.io/_apis/public/gallery/publisher/${publisher}/extension/${extension name}/${version}/assetbyname/Microsoft.VisualStudio.Services.VSIXPackage

MCP Installation Issues

Manual Installation

For manually installing the MCP server, you can add this to your AI agent’s MCP configuration file:

{
  "mcpServers": {
    "pacy-devtools": {
      "command": "npx",
      "args": ["--yes", "@pacy-dev/mcp"]
    }
  }
}

Code Inspector Issues

Code inspector is showing the right file path, but the line number is wrong

1. Use @pacy-dev/devtools-plugin to configure your project.
2. If you’re using React with Vite, and if the @vitejs/plugin-react or @vitejs/plugin-react-swc is listed among the plugins, make sure @pacy-dev/devtools-plugin comes before.
3. Similarly, if you’re using Vue, Svelte or any other framework, make sure @pacy-dev/devtools-plugin comes before the framework’s plugin.