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

@civicwar/vscode-vem

v0.0.7

Published

VisualStudio Code Extension Manager

Downloads

16

Readme

Visual Studio Code Environment Manager

THIS IS IN ALPHA. MIGHT BREAK STUFF!

Goal

This package manages a custom set of environments for Visual Studio Code.

Usage

List of Available Commands

  -s, --set <Extension Name>   Sets the Extension Environment
  -n, --new <Extension Name>   Creates a new Extension Environment
  -u, --use <Extension Name>   Starts vscode with the selected Extension Environment
  -l, --list                   Lists already created Extension Environments
  -r, --rem <Extension Name>   Deletes an Extension Environment
  -h, --help                   Prints this Help
  --install <Extension PATH>   Prepares Everything for the First Runtime

Features

Re-uses the extensions from the default environment to new environments, so you can always use the same base features.

Procedures

  • run the installation script, to be sure we have everything to work with.
    • code-em --install /Users/dfernandes/.vscode
[Install] : Removing Previous Extensions...
[Install] : Found 2 Installed Extensions...
[Install] : Clearing db if exists...
[Install] : Checking if /Users/dfernandes/.vscode Exists...
[Install] : Successfully Installed!
  • you can create new Environments
    • code-em -n Angular
[Create] : Moving base extensions to new Environment
[Create] : Created the Environment Angular Successfully
  • ...as many as you want
    • code-em -n PHP
[Create] : Moving base extensions to new Environment
[Create] : Created the Environment PHP Successfully
  • you can list the available environments
    • code-em -l
┌─────────┬───────────────────────────────────┐
│ Name    │ Path                              │
├─────────┼───────────────────────────────────┤
│ Angular │ /Users/dfernandes/.vscode/Angular │
├─────────┼───────────────────────────────────┤
│ PHP     │ /Users/dfernandes/.vscode/PHP     │
└─────────┴───────────────────────────────────┘
  • you can remove the environments by name
    • code-em -r PHP
[Remove] : Found : PHP
[Remove] : Checking if /Users/dfernandes/.vscode/PHP exists...
[Remove] : Removed Successfully
  • you can open a new VSCode window using those created environments
    • code-em -u Angular
[UseCode] : Starting code with : Angular@/Users/dfernandes/.vscode/Angular