Terminal Path ResolverFix no-match file paths in your terminal error logs.
Example: Before: After: Open file paths from the terminal: Cmd-click (on Mac) or Ctrl-click (on Windows/Linux) any file path shown in the terminal to open that file in your editor—even if the path doesn’t exist exactly on your system. Works in monorepos: Finds and opens files by searching all folders in your workspace for files that match the name and extension, making it easy to handle paths from CI or different machines. Manual path opening: Select any file path in your editor, then run the "Terminal Path Resolver: Open File Path" command from the command palette to jump directly to the file. Use CaseWhen working in a monorepo or with error logs from CI/Docker, file paths often reference locations that don't correlate to the exact path in which it exists on your local machine: Terminal Path Resolver intercepts these links and resolves them to your actual workspace location. Supported File TypesJavaScript/TypeScript: Web/Frontend: Data/Config: Backend: Systems: Other: InstallationInstall from the VS Code Marketplace or install the
Run LocallyTo test or contribute to Terminal Path Resolver locally:
Tip: Use LicenseMIT Notesshipped out of desperation by noah, in collab with may.inc reach out to info@may.inc for bugs, questions, or improvments star the repo if helpful :)! |