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

ocean-ui

v1.0.0

Published

Ocean UI

Downloads

1

Readme

this 'libary/package' first and foremost is a package of /principles/, patterns, designs, guidelines. then comes the implementation (css, stylus, react comps, etc...)

so this might be the 'library' package of reusable components. possibly useable in a completely different website, so that's why it's at the very top, completely on its own.

though this will probaby rely on styles too. mabye they'll get put together...? intersering.

need a good name. probably an element. carbon-ui, silicon-ui, cesium-ui, style-ui, ocean-ui,

black-ui

white-ui

possblye use rollup

will styles & components be seaparate npm (package.json) packages?

components/react componets/vue components/......????????

all component variations depend on styles....

import { thing } from 'ui/react' import 'ui/css' import 'ui/styl'

@import 'ui/stylus'

and then the scss version...

should there be components/ styles/ 'abstract' folder at the bottom? framework stuff vs componentized stuff?