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

vscode-framework

v0.0.18

Published

<!-- > :fire: The fastest way to develop extensions for VSCode -->

Downloads

21

Readme

VSCode Frameworkbeta

Full-featured set of tools to develop VSCode extensions with speed and minimal friction.

  • 💡 Not Boilerplated
  • ⚡️ Auto Reload
  • 🔑 TypeScript Types from package.json Contribution Points
  • ⚙️ Use TypeScript type for configuration instead of schema in package.json
  • 📦 Publish Production-ready Build with zero config
  • 🚀 Use console methods in production (creates extension output for you)
  • 🛠️ Highly Configurable

Usage

  • Install it in your project: npm i vscode-framework -D

Brief Overview

import vscode from 'vscode'

export const activate = (ctx: vscode.ExtensionContext) => {
    ctx.subscriptions.push(
        vscode.commands.registerCommand('extension.command', () =>
            vscode.window.showInformationMessage(`Debug is ${vscode.workspace.getConfiguration(extension).get<true>('enableDebug') ? 'enabled' : 'disabled'}`),
        ),
    )
}

With this framework:

import vscode from 'vscode'
import { getExtensionSetting, registerExtensionCommand } from 'vscode-framework'

export const activate = () => {
    // typesafe. ready for refactors
    registerExtensionCommand('command', () =>
        vscode.window.showInformationMessage(`Debug is ${getExtensionSetting('enableDebug') ? 'enabled' : 'disabled'}`),
    )
}

Even More Features

  • access extension context anywhere via extensionCtx export

Why it was Created?

There are several things that I don't really liked, but one of the important parts was the boilerplated generator-code.

Also, web extensions must be bundled into a single file, so just let the included esbuild do all the work.