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-auto-update

v1.0.6

Published

VSCode library that allows private extensions to automatically update

Downloads

61

Readme

VSCode Auto-Update

VSCode library that allows private extensions to automatically update

How to use

  • install package (vscode-auto-update)
  • import checker import { AutoUpdateChecker } from 'vscode-auto-update'
  • add relevant fields to package.json
  • start checker new AutoUpdateChecker({ ... }) (check options for params)
  • you're good to go

Package.json config

To use this extension, ensure the following:

  • Your package.json file contains a publishConfig field that contains a registry value. (use https://registry.npmjs.org/ when using NPM)
  • The uploaded packge contains exactly 1 .vsix file (does not matter where).

Options

  • config.friendlyName (string) - Friendly name of extension, is displayed to the user when prompting for update permission
  • config.requireUserConfirmation (bool) - Whether to wait for user approval or to just install immediately
  • config.forceUpdateOnTag (string, optional) - If provided, force update without asking for user confirmation if a version with the given tag exists in the registry. See npm docs for more info on dist tags.
  • config.onCheckFail ('notify'|'ignore') - Warn the user when checking fails or not. Ignore is generally best here since the user being offline should not warrant a warning.
  • config.onUpdateAvailable (callback, optional) - Optional callback that can change behavior of installation
  • config.onUpdateInstalled (callback, optional) - Optional callback that can change behavior after updating
  • config.checkInterval (number, default 1 hour) - Interval by which checking occurs
  • config.remote (object) - contains info about remote to use
  • config.remote.context (ExtensionContext) - VSCode extension context. Used to determine remote (see below).

Change Log

1.0.6

  • Add onUpdateInstalled callback

1.0.5

  • onUpdateAvailable can now return a promise

1.0.4

  • Reduce reload wait time even more (5s to 3s)
  • Make it so on-extensions-changed listener is placed before install action.

1.0.3

  • Support force-updating

1.0.2

  • Reduce reload wait time (from 10s to 5s)

1.0.1

  • Reduce unnecessary files in package
  • Include sourcemap

1.0.0

  • Initial release