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-scripts

v1.0.8

Published

Configuration and scripts for VS Code extension development

Downloads

20

Readme

vscode-scripts

This is a package that can be installed in a VSCode extension to add scripts for building and running the extension. It is analogous to 'react-scripts' in a Create React App project.

Assumptions

The package assumes you are using Typescript. It also assumes the following basic entry points to be defined:

node/activate.ts

Whatever default export function is defined here, will be called when the extension is activated. This is the entry point for the extension and runs in a Node environment. You have access to the state and can call arbitrary VSCode APIs from here.

state.ts

Use this entry point to define and export a Zustand 'StateCreator' that will be used to create a shared state to be synced across all processes / views.

views/{view-name}

Each file in this directory will be compiled into a separate webview. The file extension determines the framework that will be used to compile the view. For example, if you are using React, you can create a new file called src/views/my-view.tsx and it will be compiled into a webview. If you are using Svelte, you can create a new file called src/views/my-view.svelte and it will be compiled into a webview. Whatever framework you choose, ensure that the corresponding FRAMEWORK variable is set in the .env file.

Frontend components defined here have access to the Zustand store and (indirect) access to the VSCode API's via the getChromiumStore function exported from this package.

package.json
src/
    node/
        activate.ts
    views/
        my-view.(tsx|svelte)
        ...other arbitrary views
    state.ts

Usage

Once installed, you can run define the following commands in your package.json:

{
  "scripts": {
    "start": "vscode-scripts start",
    "build": "vscode-scripts build"
  }
}