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

react-native-ameelio-library

v2.1.11

Published

Components used in Ameelio's mobile suite.

Downloads

7

Readme

react-native-ameelio-library

Getting started

Clone this repo, then run npm install to get dependencies.

Run npm run start to launch the expo server. Install the Expo app for Android or iOS, and then connect your phone to the expo server to view the Storybook.

Publish the package with npm run release

Creating a component

In the src folder, identify or create a higher level folder that your component fits well under. Usually, this is the name of whatever section it falls under in the component library section of the figma.

Create a file YourComponent.react.tsx. The component should be entirely self-contained in this file (except assets). As much as you can, use colors, spacings, and stylings from the styles folder. If you component needs a color / spacing / style that is not in a GlobalStyle file but you think would make a good addition, feel free to add it. Do try to stick to naming conventions observed in those files.

Be sure to add a line in src/index.ts importing / exporting your component, organized with other components of the parent directory. This is important so that when the source code is used to build the npm repository, your code is correctly included.

Creating a story

During development, you will likely want to make a story to test your component. Stories go in the storybook/stories folder, and should be sorted into folders to mirror the structure of the src directory. Story files should end in .stories.tsx. The story should be named <ParentDirectory>/<Component>. For example, the story for the Header component in the Typography folder is named Typography/Header.

To get your story to show up in the app, you will need to add import './stories/<ParentDirectory>/<Component>.stories'; to storybook/index.js. For the sake of organization, please keep these imports alphabetical by name of story. This structure preserves the higher level structure of the components and makes them easier to find.