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

@niek-peters/supasvelte

v1.1.1

Published

A simple library that puts Realtime Supabase data into Svelte stores

Downloads

25

Readme

SupaSvelte

A simple, typesafe library that syncs Supabase Postgres data with Svelte stores in real time. Inspired by SvelteFire.

<script lang="ts">
  // ...imports
  // ...initialize Supabase client

  // get realtime data from the messages table
  const messages = getTableStore<Message>(supabaseClient, 'messages');
</script>

{#each $messages as message}
  <p>{message.text}</p>
{/each}

Features

  • Keep Svelte stores up to date with realtime database updates
  • Automatically subscribe and unsubscribe from Supabase Realtime updates
  • Provide your own or Supabase generated types for a completely typesafe experience:
getTableStore<Message, NewMessage, MutateMessage>(supabaseClient, "messages");
  • Use methods on the store to easily modify the database tables:
const messages = getTableStore(supabaseClient, "messages");

const entry = {
  id: 1,
  text: "Hey there!",
};

// adds an entry to the table
messages.add({ text: entry.text }); 

// removes an entry from the table
messages.remove(entry.id); 

// mutates an existing entry in the table
messages.mutate(entry.id, { text: "New message" }); 
  • Provide your own table index or primary key by setting the indexName option:
const messages = getTableStore(supabaseClient, "messages", {indexName: "uuid"});
  • Decrease the amount of database requests by setting the mutateInterval option. This broadcasts changes to all connected clients without updating the database in case mutate requests are sent faster than the interval. After the interval is over or a client disconnects, the database will be updated. Useful for decreasing the load on the database for applications that make very frequent mutations to persistent data.
// Set a 10 second table mutation interval
const messages = getTableStore(supabaseClient, "messages", {mutateInterval: 10000});
  • Run code after the mutation broadcasting channel is ready to receive updates using the onReady callback function:
const messages = getTableStore(supabaseClient, "messages", {indexName: "id", mutateInterval: 2000}, () => {
  console.log("Ready to broadcast!");
});

Install

SvelteKit: npm i -D @niek-peters/supasvelte

Svelte: npm i @niek-peters/supasvelte

Notes

  • This package is intended for client-side use
  • The traditional set and update methods from writable stores are intentionally unavailable
  • This package is still highly experimental and will probably change a ton in the near future. Use at your own risk!