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

r3-lib

v0.8.2

Published

## _Standardizes flow and visuals for Norce Flight (> 5.14) projects_

Downloads

29

Readme

R3-Lib

Standardizes flow and visuals for Norce Flight (> 5.14) projects

Work in progress ⚠️

TODO

-[x]Change BoxContent from arg -> children (using ContentPositioner instead)

  • Add/use Fontawesome
  • Folder with own types (if they are generall otherwise they should live in component)
  • Check handeling of fragments in GQL ( dependencies to core aso )
  • [x]Create Animation wrapper (with a few animation styles)
  • Teleprompt component (automatically types text)
  • [x] ScrollSnapper
  • MarqueeSlider (Finntack)
  • General close button + clickcallback
  • General context for lib
  • Count down component
  • Form component ( submit url, children with title, input, validation )
  • Documentation goal -> Complete Storybook
  • Documentation start -> Add docs to route for dev/stage, add content renderer with components and show info using json
  • Add slightly zoom in on image hoover ( use style and Animation wrapper )
  • AddToCartButton (Radne)
  • QtyAdjuster (Radne)
  • Checkbox (Radne)
  • [x]Progressbar
  • [x]ShakeStyle
  • NotFoundPage
  • R3-provider (contains all contexts)
  • Device testing
  • [x]UseJsonFetch
  • Add regex to CE components
  • UI page - presents all components
  • [x]ScriptLoader
  • [x]ScriptLoaderAttributes (files + json)
  • PopupTrigger
  • Payment icons
  • [x]Seo components
  • Price history component
  • [x]Accordion component
  • AccordionBlock ce components
  • Change all px -> rem
  • [x]Loader/spinner
  • Use lottie animations ?
  • [x]Curtain component
  • [x]Popup component
  • PartyTown 🎉
  • Add notification handler (Toastify?)
  • Notification component
  • Add AutoAnimate
  • HeadlessUI ( [x]Dialog implemented )
  • [x]MaxWidth component
  • ContentColumns component (Radne)
  • Add H1 bool for Hero and Box
  • Add general tracking
  • Add video hero
  • Add video box
  • Add Parakllax component ( using SwiperJS)
  • Add license to package.json

Installation

R3-Lib requires:

Install the package.

  • not implemented yet
yarn add r3-lib

Adding component

For adding new component use existing project structure. Naming convention: CamelCase.

  • Add a folder width same name as component.
  • Add a TypeScript file (Component (ExampleComponent.tsx))
  • Add a JavaScript file (CSS style, use suffix .style before .js (ExampleComponent.style.js))
  • Add a JavaScript test file (Jest test file (ExampleComponent.test.js))

Component styling file

  • import { css } from 'linaria'
  • Create an exported const width component name and suffix "Style" (const exampleComponentStyle = css``)

The end