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

cegli

v0.2.39

Published

Cegli [tzeyglee] stands for CEltra GUI Library. It's a collection of UI bricks we use at Celtra.

Downloads

308

Readme

Dashboard Pattern Library

Live demo

Please visit our Pattern Library Site for a live demo.

Running it locally

You can see everything on the live demo. Setup a local environment only for development purposes.

Dependencies

  • Ruby 2.1.5+
  • RubyGems
  • NodeJS

Install Jekyll

If you don't have bundler installed, install it with

[sudo] gem install bundler

and then

bundle install

On OS X you'll probably have to use sudo.

Install node packages

npm install

Running the platform

Compile

We're using gulp to compile CoffeScripts and less files and to arrange assets so they can be picked up by Jekyll.

npm start

Once gulp starts it will watch for any changes made to your files and recompile automatically if needed.

Start the server

Open a second terminal window and startup Jekyll.

bundle exec jekyll s

Jekyll generates a static web page based on the source files. Use --no-watch to not re-generate whenever the source files change.

Open the library in browser

By default the server is running on 0.0.0.0 at port 4000.

Start up your browser and head to http://localhost:4000. If you're running jekyll on a VM open http://{ip_of_your_VM}:4000.

Publishing to NPM (cegli)

First bump version in package.json and then

npm publish # npm login if not logged in

Problems with publishing

You need to have correct registry URL Setup

npm config get registry
# if http://npm.celtra.com/ then:
npm config set registry http://registry.npmjs.org/

Prepublishing

Sometimes you need to publish a package before it's ready to be released. We're using npm tags to do this.

First bump package version and assign a tag to it.

npm dist-tag add [email protected] beta

Check if tag is assigned.

npm dist-tag ls

latest: 0.1.15
beta: 0.1.16

Once a version has a custom tag assigned it's ready to be prepublished. Publishing a package sets the latest tag to the published version unless the --tag option is used

npm publish --tag beta

Now you can use tag instead of version to install package.

"dependencies": {
	"cegli" : "beta"
}
npm install cegli --tag beta

Don't forget to clear the tag once you're done.

npm dist-tag rm cegli beta

Updating live demo

The gh-pages branch is specially configured to run on github pages and will not run on your local environment. Make sure you never directly commit to gh-pages. You should instead first update the master and then merge to gh-pages branch. This way we keep all changes in master and it's harder to break the live demo. Run gulp build before committing to gh-pages branch.

Developer notes

  • All folders with the _ prefix are ignored by jekyll and not copied to _site.
  • Run gulp clean if you get an error similar to the one bellow when trying to switch the branch.
Untracked working tree file 'build/fonts/avenirnextltpro-light-webfont.ttf' would be overwritten by merge.