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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@getloom/svelte-gettable-stores

v0.2.3

Published

`.get()` for Svelte stores; please do not use unless you know what you're doing

Readme

@feltcoop/svelte-gettable-stores

⚠️ use runes instead!!

npm: @feltcoop/svelte-gettable-stores

‼ This library can cause tricky bugs and there may be good reasons the Svelte team supports get and not .get(). (some discussion on this issue) Please do not use this unless you know what you're doing 🤒 The only benefit is performance, which may not be relevant for your usage.

Adds a non-reactive .get() to Svelte stores (as well as @feltcoop/svelte-mutable-store). It copypastes the original implementations and makes these changes and then this derived followup.

See the tests for more. The derived implementation was mostly copied from svelte-store2. Discussion is welcome in issues and privately.

motivation

Svelte offers the standalone get function to non-reactively access store values, but it costs more than necessary in most cases. From the Svelte docs:

"This works by creating a subscription, reading the value, then unsubscribing. It's therefore not recommended in hot code paths." (svelte.dev/docs)

In many cases, this cost is either negligible or architecturally irrelevant. In other cases, like nested stores and collections processed in non-reactive contexts like event handlers, the cost can be undesirably high.

This library adds .get() to the original store implementations to access values without the cost of a subscription+unsubscription in all cases except derived stores with zero subscribers. In that case, it uses the get builtin.

license

MIT (copy of Svelte's license)

everything else: Unlicense (public domain)