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

github-web-launcher

v0.3.0

Published

Launching from command line to GitHub

Downloads

4

Readme

GitHub Web Launcher CircleCI

not the webdriver-manager cli

Using Github Web Launcher

Install globally:

npm install -g github-web-launcher

In a git repo folder via command line:

web

Why just web, because its short and easy to remember.

Example using GitHub Web Launcher

An example of using it:

In the terminal, in the protractor repository, under the folder path protractor/lib/driverProviders/ typing in web by default will navigate to the origin master url on GitHub found in the .git/config and navigate to the folder lib/driverProviders.

The result is https://github.com/cnishina/protractor/tree/master/lib/driverProviders

The contents of the .git/config is as follows:

[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
	ignorecase = true
	precomposeunicode = true
[remote "origin"]
	url = [email protected]:cnishina/protractor
	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
	remote = origin
	merge = refs/heads/master
[remote "upstream"]
	url = [email protected]:angular/protractor
	fetch = +refs/heads/*:refs/remotes/upstream/*

If this is the first time running it, it will download ChromeDriver, launch Chrome and navigate to chrome://version. It will parse the command line for Chrome and navigate to the url above.

Roadmap

Command line support for:

web <file> <remote> <branch>

View README.md in the default origin master:

web README.md

View a file or folder relative to the current directory assuming it is in the repository. In the following example, the current folder is lib.

web ../some/path/to/file_or_folder_1 
// github path = lib/some/path/to/file_or_folder_1

web some/path/to/file_or_folder_2
// github path = lib/some/path/to/file_or_folder_2

View a file or folder from the base of the repo, independent of where you are located in the repo.

web /some/path/to/file_or_folder

View the current directory for the upstream remote on a default master branch.

web . upstream

View the usptream remote and branch foobar

web <file_or_folder> upstream foobar