JavaScript Package Inspector

Motivations

Published packages don't always include a link to their source on GitHub.

The linked repository is not necessarily representative of published package.

Usage

Package root provides links to all available versions, and highlights the one tagged as latest .

https://npmfs.com/<name> https://npmfs.com/package/<name>

When viewing a package on npm, it is conveniently accessible with a one-char edit to the page url.

https://www.npmjs.com/package/<name> https://www.npmfs.com/package/<name>

Specific package versions can be accessed directly.

https://npmfs.com/package/<name>/<version>

Directories and files inside the package are viewed by appending the path.

https://npmfs.com/package/<name>/<version>/<path> https://npmfs.com/package/<name>/<version>/example/ https://npmfs.com/package/<name>/<version>/example/index.js

Package diffs ( version-0 .. version-1 ) are viewed by navigating to the root directory of version-0 , clicking on the diff link in the top right, and selecting version-1 in the version list.

https://npmfs.com/compare/<name>/<version-0>/<version-1>

In this compare view, line numbers are a shortcut to their respective file's source.

are found on the right side of lines in both the file and diff views. These links will add a hash to the url which scrolls the browser to the selected line, and highlights it.

https://npmfs.com/package/<name>/<version>/index.js#<line> https://npmfs.com/compare/<name>/<version-0>/<version-1>#<line>

More precise selections can be created by editing the URL's hash. These can link to line ranges and highlight specific substrings within a line.

The sticky header sections contain useful links to navigate between pages.