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

yafsn

v0.2.5

Published

Yet another svelte navigator

Downloads

9

Readme

/yafsn/ - yet another svelte navigator

npm NPM Svelte

Motivation

There is a lot of navigation solutions for svelte but many of them are somewhat complicated/or they provide more features than you need with a bunch of extra steps to even begin.

  • Do you need "production ready" solution for navigation?
  • Do you need accessibility?
  • Do you need SSR?
  • Do you need "insert feature you won't ever use"?

If your answer to the questions above is NO, then you are in good place.

Installation

npm install yafsn

Usage

Try it here

// App.svelte
<script>
  import { setContext } from "svelte";
  import { createNavigator, makeScreen } from "yafsn";

  import A from "./A.svelte";
  import B from "./B.svelte";

  const screens = {
    A: makeScreen({ component: A }), // Custom screen options
    B: makeScreen(B) // or simplified form
  }

  const navigator = createNavigator({
    screens,
    initialScreen: "A" // OPTIONAL, accepts route name or result of makeScreen
  });
  setContext("navigator", navigator);

  const { screen, navigate } = navigator;
  navigate("A");
</script>

<svelte:component
  this={$screen?.component}
  {...$screen?.props}
/>
// A.svelte - first screen

<script>
  import { getContext } from "svelte";
  const { navigate } = getContext("navigator");

  export let text = "World";

  function goToB() {
    navigate("B");
  }
</script>

<p>Hello {text}</p>
<button on:click={goToB}>Go to B</button>
// B.svelte - second screen
<script>
  import { getContext } from "svelte";
  const { navigate } = getContext("navigator");

  function goToA() {
    navigate("A", { text: "Earth" });
  }
</script>

<p>When we go back to A, Hello World will become Hello Earth</p>
<button on:click={goToA}>Go to A</button>

Helper components

This library exposes simple bare-bones navigator which you can tweak as much you like but if you want to just plug in the screens and call it a day there are some helper components.

Before using helper components make sure to dedupe svelte and yafsn dependency! See: rollup, vite

Try it on CodeSandbox

Navigator wrapper

<script>
  import { makeScreen } from "yafsn";
  import Navigator from "yafsn/components/Navigator.svelte";

  import A from "./A.svelte";
  import B from "./B.svelte";

  const screens = {
    A: makeScreen({ component: A }),
    B: makeScreen(B)
  }

  // All of the screen can access navigator with getContext("navigator")
</script>

<Navigator
  options={{
    screens,
    initialScreen: "A"
  }}
/>

License

MIT