npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

blade-lsp

v0.2.0

Published

Language Server Protocol implementation for Laravel Blade templates

Readme

Laravel Blade LSP

Built with TypeScript, Node.js, and tree-sitter-blade.

Installation (Development)

# Clone the repository
git clone https://github.com/gcavanunez/blade-lsp.git
cd blade-lsp

# Install dependencies
npm install

# Build
npm run build

Neovim Configuration

Mason (Recommended)

Install via Mason using the blade-lsp-mason registry:

require("mason").setup({
  registries = {
    "github:gcavanunez/blade-lsp-mason",
    "github:mason-org/mason-registry",
  },
})

Run :MasonUpdate to refresh registries, then :MasonInstall blade-lsp.

Once installed, configure the LSP using vim.lsp.config (Neovim 0.11+):

vim.lsp.config('blade_lsp', {
  cmd = { 'blade-lsp', '--stdio' },
  filetypes = { 'blade' },
  root_markers = { 'composer.json', 'artisan', '.git' },
})

Manual

If you prefer not to use Mason, clone and build the project, then point directly to the built server:

vim.lsp.config('blade_lsp', {
  cmd = { 'node', '/path/to/blade-lsp/dist/server.js', '--stdio' },
  filetypes = { 'blade' },
  root_markers = { 'composer.json', 'artisan', '.git' },
})

Update /path/to/blade-lsp/dist/server.js to the actual path where you cloned and built the project.

Initialization Options

You can pass init_options to configure the LSP server's behavior:

vim.lsp.config('blade_lsp', {
  cmd = { 'node', '/path/to/blade-lsp/dist/server.js', '--stdio' },
  filetypes = { 'blade' },
  root_markers = { 'composer.json', 'artisan', '.git' },
  init_options = {
    -- string[]|nil (default: auto-detected)
    -- Explicit command array to execute PHP. When omitted, the server
    -- auto-detects by probing: Herd, Valet, Sail, Lando, DDEV, Local, Docker.
    phpCommand = { 'docker', 'compose', 'exec', '-T', 'app', 'php' },

    -- "herd"|"valet"|"sail"|"lando"|"ddev"|"local"|"docker"|nil (default: auto-detected)
    -- Preferred PHP environment. When set, skips auto-detection and
    -- tries only the specified environment.
    phpEnvironment = 'docker',

    -- boolean|nil (default: true)
    -- Enables Laravel project integration (views, components, custom directives
    -- via PHP). Set to false for standalone Blade support only.
    enableLaravelIntegration = true,

    -- boolean|nil (default: false)
    -- Enables the embedded PHP bridge for `<?php ... ?>` and `@php ... @endphp`
    -- regions inside Blade files.
    enableEmbeddedPhpBridge = false,

    -- "intelephense"|"phpactor"|"phpantom"|nil (default: "intelephense")
    -- Selects the downstream PHP backend used by the embedded bridge.
    embeddedPhpBackend = 'phpactor',

    -- string[]|nil (default: backend-specific command)
    -- Explicit command array for the embedded PHP backend.
    embeddedPhpLspCommand = { '/home/you/.local/share/nvim/mason/bin/phpactor', 'language-server' },

    -- Backend-specific bridge configuration.
    intelephense = {
      initializationOptions = {
        globalStoragePath = vim.fn.expand('~/.local/share/intelephense'),
        storagePath = vim.fn.expand('~/.local/share/intelephense'),
      },
      settings = {
        intelephense = {
          client = {
            autoCloseDocCommentDoSuggest = true,
          },
          files = {
            maxSize = 10000000,
          },
        },
      },
    },

    phpactor = {
      initializationOptions = {
        ['language_server_phpstan.enabled'] = false,
        ['language_server_psalm.enabled'] = false,
      },
    },

    -- PHPantom runs over stdio with no required initialization options.
    -- If it is not on PATH, point this at the built binary, for example:
    -- embeddedPhpBackend = 'phpantom',
    -- embeddedPhpLspCommand = { '/home/you/phpantom_lsp/target/release/phpantom_lsp' },
    phpantom = {
      initializationOptions = {},
    },
  },
})

Embedded PHP Bridge Notes

  • The embedded PHP bridge supports phpactor, intelephense, and phpantom as downstream PHP backends.
  • phpactor has been the most exercised backend for practical class completion/import flows such as:
    • User -> User (App) -> use App\Models\User;
  • intelephense support remains available, but is currently more experimental/weaker in this embedded bridge mode.
  • phpantom uses the existing shadow-PHP bridge path today. PHPantom also has native Blade support, which could be used by a future native backend mode that bypasses shadow files.
  • The currently supported happy path is bare class completion in Blade PHP regions; namespaced completion forms like \App\Models\U are still being explored.

Credits

This project draws inspiration from and utilities from:

License

MIT