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

svelte-context-deeznuts

v1.0.1

Published

![deeznuts](https://github.com/tncrazvan/svelte-context-deeznuts/blob/main/deeznuts.jpg?raw=true "deeznuts")

Downloads

2

Readme

deeznuts

Introduction

Svelte Context Deeznuts is a very advanced 58 line library that solves a problem that's already been solved by the svelte standard library.

Why?

It is often the case that we need to provide some type hinting for component contexts.

Unfortunately getContext does not inherit type hints from setContext and there is probably no easy way to fix that in the standard library without adding unnecessary complexity to the context api; and I like my standard libraries to be simple.

Some workarounds include creating separate files to define the typed contexts and importing them separately.

I don't like that, all component.svelte's affairs should remain in the component.svelte file.

When to use

Make sure you actually need to use the context api.

This library automatically converts your value into a Writable<T>.

Chances are that if you don't need a Writable in your context, you probably don't need the context api itself.

We may agree to disagree.

How to use

Install with

npm i -D svelte-context-deeznuts

Create you parent component and set a context.

<!-- List.svelte -->
<script lang="ts">
  import { set } from 'svelte-context-deeznuts'
  set<false | string>('activeID', false)
</script>

<ul>
  <slot />
</ul>

This will create your context.

Then export the getter from the module context.

<!-- List.svelte -->
<script lang="ts" context="module">
  import { get } from 'svelte-context-deeznuts'
  export const getActiveID = get<false | string>('activeID')
</script>

<script lang="ts">
  import { set } from 'svelte-context-deeznuts'
  set<false | string>('activeID', false)
</script>

<ul>
  <slot />
</ul>

Once that's done create your child component.

<script lang="ts">
  import { getActiveID } from './list.svelte'
  const activeID = getActiveID()
  const id = crypto.randomUUID()
</script>

<li on:mouseup={() => ($activeID = id)}>
  <span>
    <slot />
  </span>
  {#if id === $activeID}
    <span>(active)</span>
  {/if}
</li>

And to put things together:

<!-- App.svelte -->
<script>
  import Item from './item.svelte'
  import List from './list.svelte'
</script>

<List>
  <Item>item 1</Item>
  <Item>item 2</Item>
  <Item>item 3</Item>
  <Item>item 4</Item>
  <Item>item 5</Item>
</List>