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 🙏

© 2024 – Pkg Stats / Ryan Hefner

dockerfile-language-service

v0.14.0

Published

A language service for Dockerfiles to enable the creation of feature-rich Dockerfile editors.

Downloads

20,725

Readme

Dockerfile Language Service

Node.js Builds Coverage Status Build Dependencies License: MIT

This is a language service for Dockerfiles written in TypeScript. If you are looking for an actual Dockerfile language server that can be used with editors that implement the language server protocol, please visit the rcjsuen/dockerfile-language-server-nodejs repository.

The purpose of this project is to provide an API for creating a feature-rich Dockerfile editor. While this language service implements requests from the language server protocol, they are exposed as regular JavaScript functions so you can use them in the browser if you wish. For a demonstration of this language service's capabilities with Microsoft's Monaco Editor, please click here.

To install this language service as a dependency into your project, you will need to have Node.js installed.

Supported features:

  • code actions
  • code completion
  • definition
  • diagnostics
  • document highlight
  • document links
  • document symbols
  • folding
  • formatting
  • hovers
  • rename
  • semantic tokens
  • signature help

Development Instructions

If you wish to build and compile this language server, you must first install Node.js if you have not already done so. After you have installed Node.js and cloned the repository with Git, you may now proceed to build and compile the language server with the following commands:

npm install
npm run build
npm test

If you are planning to change the code, use npm run watch to get the TypeScript files transpiled on-the-fly as they are modified.

Installation Instructions

To add this language service into your project, you must add dockerfile-language-service as a dependency in your package.json file.

Browser Example

The /example/ folder includes an example for using this language service in a browser as a static HTML page with JavaScript. To build the example, please run the following commands from the root of the project:

npm install
cd example
npm install
npm run build

As the example naturally relies on the language service, it is necessary to invoke npm install on the root folder first before invoking npm install in the /example/ folder. Once npm run build has completed, you can open the /example/lib/index.html in a browser to test things out!