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

x4-script-language-server

v0.9.2

Published

Language Server Protocol server for X4: Foundations scripts (AI scripts and Mission Director scripts).

Readme

x4-script-language-server

Language Server Protocol server for X4: Foundations scripts (AI scripts and Mission Director scripts), built on x4-script-core. The X4CodeSense VS Code extension bundles it; any other LSP client can start it with npx x4-script-language-server --stdio, or with --node-ipc when it forks the server as a Node.js process.

Settings are read from the x4CodeSense configuration section with workspace/configuration, which the client must support: settings sent in initializationOptions or in the settings of workspace/didChangeConfiguration are not read, the notification only makes the server ask again. The game files come from unpackedFileLocation (the extracted files) or, when it is empty, from gameFolder (an installed game, read from its catalogs in place). A file of an installed game's catalogs has no file on disk, so every place the server sends in one has the read-only scheme x4codesense-game with the file's path in the game folder, x4codesense-game:/md/setup.xml; the client asks for its text with the x4codesense/gameFile request, and such a document opened is analysed as that file. Documents with the language id lua only get a hover between the parentheses of ReadText(page, id), with the text it reads. Documents with the schemes x4codesense-patch and x4codesense-patched are the two sides of a patch comparison, the file a patch changes before and after it, with the patch document's uri in the patch parameter of the query: they are analysed as that file, and only the side after the patch gets diagnostics, those the side before it does not have.

Part of X4CodeSense. Apache License 2.0.