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

@forinda/kickjs-view-language-server

v0.4.1

Published

Language server for KickJS .kick views — diagnostics, completion, hover, definition and formatting from the runtime's own parser and checker

Readme

@forinda/kickjs-view-language-server

A language server for KickJS .kick views, built on Volar.

  • Errors as you type, from the same parse + check the runtime uses.
  • Completion for @ keywords, pipes, components and their inputs, layout and slot names, and names in scope.
  • HTML, CSS and Emmet inside templates.
  • Hover, go to definition, find references and formatting.
  • Rename pipes, components and layouts across templates; renaming a template file updates its uses, ctx.render('…') calls in TS / JS included.
  • Semantic tokens, so any LSP editor highlights the template syntax.
  • In TypeScript and JavaScript files, template names in ctx.render('…') and views.render('…'): completion, go to definition, and a warning for a name with no template. Nothing else in those files is touched.

When the client says the workspace is trusted, it loads the project's own @forinda/kickjs-view so the editor agrees with the build, and falls back to its bundled copy (with one warning) when the project has none.

Use

The KickJS VS Code extension bundles this server. Any LSP client can run it: setups for Neovim, Vim, Helix, Emacs and JetBrains IDEs are in .kick in other editors.

pnpm add -D @forinda/kickjs-view-language-server
npx -y -p @forinda/kickjs-view-language-server kick-view-ls --stdio

kick-view-ls is the command, not a package name. Without -p, npx finds it only when it's installed in the project the editor starts it in; otherwise npx looks for a package called kick-view-ls and fails with a 404.

Initialization options, relative to the workspace folder:

| option | default | | --------------- | ------------------------------------------------------------------------------------------------ | | viewsDir | src/views | | componentsDir | components | | pipesFile | <viewsDir>/pipes.ts | | layout | none — the same as createViews({ layout }): one name, or folder prefix → layout | | baseLayout | none — the same as createViews({ baseLayout }) | | trusted | false — only true imports the project's @forinda/kickjs-view (its code runs in the server) |

Any file ending in .kick is a template, whatever languageId the editor sends. The custom request kick/templateNames returns every template name except components.

See the views guide.