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

svelte-maybe-transition

v0.1.2

Published

Super-simple Svelte transition utility for on-the-fly enabling and modification of element transitions

Downloads

2

Readme

svelte-maybe-transition

A super-simple Svelte transitions utility that allows on-the-fly enabling and modification of element transitions.

Why? Although you could achieve this with if/else blocks, that would require duplicating markup and logic. This util allows for stock Svelte transitions syntax, but with added 'enable' and 'fn' params that can be changed on the fly. I needed something for my own project that allowed changing transition functions programmatically, and this seemed like the best way to do it.

Installation

Using NPM:

npm install --save-dev svelte-maybe-transition

Using Yarn:

yarn add -D svelte-maybe-transition

Basic usage

<script>
  import { maybe } from 'svelte-maybe-transition';

  // Let's assume that your PageLoad data has a boolean 'transitions' property
  export let data;

  $: enableTransitions = data?.transitions;
</script>

<div
  transition:maybe={{
    enable: enableTransitions,
    fn: 'fly',
    y: -100,
    duration: 1000
  }}
>
  Look at me!
</div>

API

maybe()

Accepts fn parameter of 'blur' | 'fade' | 'fly' | 'slide' | 'scale' | 'draw', and an enable boolean. Other than those two, the parameters required vary by which transition function is specified - if in doubt, check out Svelte's transition documentation!

maybeCrossfade()

Since Svelte's crossfade transition is a bit special it's split into its own function. It accepts normal animation params, plus the aforementioned enable boolean, and returns an array of two unnamed functions: send and receive.

Usage

<script>
  import { maybe, maybeCrossfade } from 'svelte-maybe-transition';

  const enable = true,
    commonParams = {
      enable,
      duration: 500,
      delay: 250
    };

  // Since 'crossfade' requires a fallback transition if there is no element to send
  // or no element to receive, we construct a fallback 'maybe' fade transition here
  const fallback = maybe({
    fn: 'fade',
    ...commonParams
  });

  $: [send, receive] = maybeCrossfade({
    fallback,
    ...commonParams
  });
</script>

{#if condition}
<h1 in:send="{{key}}" out:receive="{{key}}">BIG ELEM</h1>
{:else}
<small in:send="{{key}}" out:receive="{{key}}">small elem</small>
{/if}

Contributing

Pull requests are welcome. For major changes, or any issues, please open an issue first.

Building

Building the package is done with yarn build, which outputs built files to ./package.

Building the demo app is done with yarn build:app, which outputs static HTML to ./.svelte-kit/build.

License

See LICENSE.md