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 🙏

© 2026 – Pkg Stats / Ryan Hefner

velocity-ui

v0.0.2

Published

Minimalistic & simplistic UI components for React Native

Readme

Velocity-UI

Minimalistic & simple UI.

A library containing React Native components that do what it should do in a performant manner. A compilation of components based on other components that I have worked with but did something strange that I did not expect. This library aims to do them justice while trying to retrofit them with any design without much negative impact.

Components

Virtualized Grid

The virtualized grid only renders items as it comes into view to maintain a level of usability when rendering and scrolling. Out of view components are replaced with blank, same sized View components to reduce rendering load.

Props

Prop | Default | Type | Description -----|---------|------|------------ dataArray | - | array | Array of items to be rendered. numColumns | 1 | number | Number of columns to divide the items into. renderItem | - | function | Function to render each data item as a component. Takes a single data element from dataArray and the index number as parameters. horizontal | false | bool | Use the grid horizontally. (Optional) useShortRadius | false | bool | When determining an item's collision radius, use the shortest dimension instead. (Optional) keyExtractor | - | function | Function to pull out the key for each child component rendered. Takes a single data element from dataArray as the parameter. collisionDetection | boundingBox | function | Function that calculates whether an item has entered the screen. Takes two component body metadata as parameters. Refer to the Utility section.

Utility

Collision Detection

The library currently provides two types of bodies for collision detection by default: bounding box and bounding circle.

Bounding box collision detection uses the standard 2D rectangular collision detection. The algorithm checks whether an edge of a rectangular body has touched or crossed the opposite edge of the other rectangular body. For example, if rectangle A's right edge has touched or crossed the left edge of rectangle B, then there is a collision. This algorithm will tend to detect the collision just in time due to the hard edges of a rectangle.

Bounding circle collision detection uses circular bodies to represent a component body. By default, rectangular components will use the longest edge as the radius for its collision body. The algorithm measures the distance between the origins of two circle bodies. A collision will be detected if the distance is equal to or less than the combined radius of the two bodies. When organized in a grid, this algorithm tends to detect collisions earlier in the centre and provides a bit of render ahead for a bit better scrolling experience.

It is also possible to use custom collision detection algorithms as components simply take the function as props. However, the limitation right now is that components will only provide rectangular or circlar collision body info.