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

@safe-fullpage/react

v1.0.0

Published

---

Downloads

30

Readme

Safe-fullpage


Simple library to let you build page with basic fullpage animation easily with fully mobile compatibilty.

For the ones who don't want to read docs but peek the taste of fullpage.

Note

For the 🐖lazy devs🐖, just remember ONE THING

  1. only one FullpageContainer per page.

Contribution

Any suggestions and PRs are welcomed.

Any of your suggestion or idea or criticizings or any advises would help me a lot.

I'll be glad to hear it.

Installing

React.js

pnpm install @safe-fullpage/react

Vanilla.js

pnpm install @safe-fullpage/vanilla

Usage

Vanilla

/*  index.html */
<body>
    <safe-fullpage-container>
      <safe-fullpage-element>
        <div class="d1"></div>
      </safe-fullpage-element>
      <safe-fullpage-element>
        <div class="d2"></div>
      </safe-fullpage-element>
      <safe-fullpage-element>
        <div class="d3"></div>
      </safe-fullpage-element>
    </safe-fullpage-container>
    <script type="module" src="/src/main.ts"></script>
</body>
/*  main.ts */
import '@safe-fullpage/vanilla'

React

import { FullpageContainer , FullpageElement } from '@safe-fullpage/react'

const Page = () => {

  return (
    <FullpageContainer>
      <FullpageElement>{/* element */}</FullpageElement>
      <FullpageElement>{/* element */}</FullpageElement>
      <FullpageElement>{/* element */}</FullpageElement>
    </FullpageContainer>
  )
}

Interface

FullpageContainer

  • enableKeydown

    type : boolean

    default : false

    description: enables triggering fullpage animation via keydown


  • scrollDelay

    type : number

    default : 1500

    description: minimum time interval between each animation


  • touchMovementThreshold

    type : number

    default : 20

    description: minimum pan movement to trigger animation ( usally for mobile devices )


  • duration

    type : number

    default : 900

    description: time taken to transition for each animation


  • timingMethod

    type : "ease" | "ease-in" | "linear" | "ease-in-out" | "ease-out";

    default : "ease"

    description: timing function, which will describe how the transition will be held


FullpageElement

  • elementType

    type : "content" | "footer;

    default : "content"

    description: Describe how scolling should be handled for current element.

    _ content : Position current element to stick to bottom of viewport

    _ footer : Position current element to stick to top of viewport

    ⚠️Warning⚠️) Do not use 'footer' unless its not literally at the end of FullpageElement List.


License

MIT