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

nicobar

v1.0.3

Published

Javascript package for theming layouts

Downloads

15

Readme

Nicobar

Javascript package for theming layouts.

NPM Version Build Status

Install

Make sure you have node and npm installed.

$ npm install nicobar

Using

Vanilla JS

Create or update your code as normal using your CSS, but if something has to change, use CSS Custom properties to set a variable.

Like this

.some-class {
   display: inline-block;
   background: var(--background, #f00);  
}

then in JS your code.

nicobar.set('.some-class', { background: '#0f0' });

you can use it how many times you want.

nicobar.set(target, data) the set method accept String or HTMLElement (for while). and the data is a Object with key as custom-property name.

React

Inject nicobar in your project

import { Nicobar } from 'nicobar'
// or
const Nicobar = require('nicobar').Nicobar;

then init on your component Component Constructor

class MyComponent extends React.Component {
  render() {
    return <Nicobar style={obj}>
      ...
    </Nicobar>
  }
}

when it is done you can only change the property style and everything will run as expected.

Contributing

  1. Fork
  2. Create your feature branch
  3. Commit your changes
  4. Push to the branch
  5. Submit a pull request

Feature branch (git checkout -b my-new-feature) | commit (git commit -m 'Add some feature') | push (git push origin my-new-feature).

License

MIT License