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

code-opener-cli

v0.1.3

Published

command line interface code opener

Downloads

6

Readme

code-opener-cli

command line interface code opener

install

$ npm i -g code-opener-cli
or
$ yarn global add code-opener-cli
or
$ pnpm add -g code-opener-cli

usage

# first set your workspaces
$ openc workspace add <pathToYourWorkspace>
# open it
$ openc <yourProjectFolderName>

tips

# show help command
$ openc --help

# If your code editor is not vscode
# then you need to change the executable command
# $folder is a placeholder and will be replaced with the corresponding path when executed.
$ openc openCMD 'idea $folder'

# It's much easier to alias a project,
# and then you can use the alias to open the project.
# for example
$ openc alias add my ~/workspace/my-project
$ openc my

config

# open folder, Similarly ** matching is possible for <folderName>, like project**
$ openc <folderName>

# print config
$ openc config

# set open command, default is "code $folder", example for idea
$ openc openCMD 'idea $folder'

# set folder alias
$ openc alias <alias> <originFolderName>
# remove alias
$ openc alias <alias>
# clear alias
$ openc alias clear
# print alias
$ openc alias print

# set workspaces
$ openc workspace add <workspacePath>
$ openc workspace rm <workspacePath>
# list workspaces
$ openc workspace ls
# clear workspaces
$ openc workspace clear

# set workspaceOnly, default true, change false will travel globally
$ openc workspaceOnly <true | false>

# set ignoreFolders
$ openc ignoreFolders add <ignoreFolder>
$ openc ignoreFolders rm <ignoreFolder>
# list ignoreFolders
$ openc ignoreFolders ls
# clear ignoreFolders
$ openc ignoreFolders clear