Skip to content

[Feature]: Search and Jump to Defined Laravel Routes in VS Code #539

@slowlyo

Description

@slowlyo

Feature Description

First of all, thank you for maintaining the official Laravel VS Code extension — it already provides great DX improvements for Laravel development.

I would like to request a feature related to route discovery and navigation.

Currently, in medium to large Laravel projects, it is often difficult to quickly locate where a specific route is defined, especially when:

  • Routes are split across multiple files (web.php, api.php, custom route files)
  • Routes are grouped with prefixes, middleware, or namespaces
  • Route definitions use closures, controllers, invokable classes, or route macros

Requested Feature

Add support for searching and jumping to defined Laravel routes directly from VS Code.

Possible capabilities (any subset would already be very helpful):

  • Search routes by:

    • URI (e.g. /users/{id})
    • Route name (e.g. users.show)
    • HTTP method (GET / POST / etc.)
  • Show route metadata:

    • Method(s)
    • URI
    • Route name
    • Controller / action
    • Source file & line number
  • Click to jump directly to the route definition

  • Optional: command palette integration, e.g.
    Laravel: Search Routes


Why This Is Useful

  • Improves navigation and code discovery in large Laravel codebases

  • Reduces reliance on manually running php artisan route:list

  • Aligns with existing IDE features like:

    • “Go to Controller”
    • “Go to View”
  • Competing editors and some community extensions already provide partial solutions, but having this built into the official extension would be a big DX improvement


Implementation Ideas (Optional)

  • Parse routes via:

    • php artisan route:list --json
    • Or static analysis of route files
  • Cache results for performance

  • Update cache on file change or via a manual refresh command

(I understand there may be technical constraints — these are just suggestions.)


Closing

Thanks again for your work on the Laravel VS Code extension.
I’d be happy to help test or provide feedback if this feature is considered.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions