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

st-link-local

v1.0.0-alpha.1.49

Published

Watches locally file:-referenced dependencies and syncs them into ./node_modules using yarn

Downloads

6

Readme

st-link-local

When working with more than one inter-dependent node modules locally, developers usually have to opt-in for npm link or yarn link.

Both solutions come with gotchas. Interference with npm caches, local vs. remote registry issues and Microsoft Windows filesystem symlink problems may occur and framework development may become a nightmare.

This simple CLI tool solves these headaches: We've introduced a new package.json field stLinkLocalDependencies:

{
    "stLinkLocalDependencies": {
        "@springtype/core": "file:../../core/dist"
    }
}

Using a custom field ensures that the link-local dependency management is not interfering with and default npm behaviour.

Run:

npx st-link-local

to install locally linked dependencies and watch/sync for any changes.

For example, you could run:

tsc -w

in ../../core/. On any file change caused by a typescript transpilation run, st-link-local will synchronize the local dependency code.