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

react-anion

v0.0.2

Published

An incomplete implementation of Ionic components in reactjs

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

thiagofelixthiagofelix

Keywords

componentsionicreactreact-componenttoolkit

Readme

Anion

NPM Package Build Status

Dependencies Dev Dependencies Peer Dependencies

Anion is an unofficial and incomplete implementation of Ionic components in reactjs.

Not ready Yet

I don't recommend to use in production If you’d like, you can contribute to help make it happen.

Installation

Anion is available as an npm package.

npm install react-anion

After npm install, you'll find all the .js files in the /components folder and their compiled versions in the /lib folder.

Demo

Check out the github.io/anion

Motivation

I always liked to use Ionic on my AngularJS projects and few weeks ago when I decided to give a try to reactjs I couldn't find a component library which were not necessarly implementing material design, so inspered by other projects I decided to create "Yet another component library for reactjs".

My goal with this project is to port over as much of the components from the awesome ionic components library as I can to the reactjs world. I am trying to keep up with the hype of local scope css, so for this I am using css-modules with sass. The build is managed by the webpack and there are no documentation by now, the best resource for reference is the demonstration page where you can take a look what is the API of the components and their usage.

I am not a react expert, honestly this is my first try implementing something generic with it, so please feel free to send me issues or recommendations, I will try my best to keep things following whatever is the best regarding the technology and best practices.

Ultimately you are very welcome to contribute however you want.

Inspirations:

Contributing

One challenge to port ionic components is that many style rules are applied based on the components hierarchy ( eg: .list .item button ) which I feel goes agains the css-modules principle of scoping all the style in the component itself and not relying on the cascading aspect of css.

I decided to initially port only the iOS styles because that is what I need the most, but I am trying to keep the same markup on the components, this way hopefully it won't be much work to include md styles in the future

I am using travis-ci to perform integration, make sure you take a look on the build status after you submit a pull request

Workspace

You shouldn't have problem to reproduce the environment locally npm install and npm start should get you up and running.

License

MIT. Copyright (c) 2015 Thiago Felix