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

component-library

v3.2.3

Published

An easy way to create HTML styleguide for your project.

Downloads

180

Readme

An easy way to create HTML styleguide for a web project.

Demo: http://sneas.github.io/component-library/index.html

travis build version MIT License semantic-release

Motivation

Most of web projects consist of components. It could be simple basic components like texts, icons, buttons or form inputs. Or complex components like video player, sophisticated inputs (i.e. typeahead), menus, popovers, etc. Any large project reaches a point when it's hard to remember and control all the pages and their components.

Component library is a special place to store and manage all the HTML components of a web site in one place.

Features:

  • easy to install
  • easy to manage
  • easy to integrate with existing project
  • absence of conflicts with existing JS and CSS

Installation

npm install component-library

Integration with project

List of components

Create an empty folder in your projects's file system and fill it with HTML files (components). One HTML file per one component.

See demo/src/templates as an example.

Integration with build process

As a reference I've used Gulp but it's easy to add components library into any build system. All you need is to require component library, point it to your newly created components folder and give it links to your projects's CSS and JS files.

var gulp = require('gulp'),
    componentLibrary = require('component-library');

gulp.task('cl', function(cb) {
    componentLibrary(
        '/project/templates/dir',
        '/project/public/component-library',
        {
            baseUrl: '/component-library/',
            favicon: {
                href: '/project/favicon.ico',
                rel: 'shortcut icon',
                type: 'image/x-icon'
            },
            js: [
                //List of your project's JS files goes here
                '/project/js/file.js'
            ],
            css: [
                //List of your project's CSS files goes here
                '/project/css/file.css'
            ]
        }
    ).then(function() {
        cb();
    }).catch(function(er) {
        cb(er);
    });
});

gulp.task('cl:watch', ['cl'], function() {
    gulp.watch(['/project/templates/dir'], ['cl']);
});

FAQ

What if my project has a custom initialization logic in layout?

Create you own layout file by copying minimum HTML required:

<!DOCTYPE html>
<html>
<head></head>
<body>
    {{ content }}
</body>
</html>

Add your custom code to it. NB: You can add only the required code. All the CSS links and JS scripts will be added automatically. Add the layout param to the configuration object. Example:

var componentLibrary = require('component-library');

componentLibrary(
    '/project/component-library/templates/dir',
    '/project/public/component-library',
    {
        layout: '/project/component-library/your-layout.html',
        baseUrl: '/component-library/',
        favicon: {
            href: '/project/favicon.ico',
            rel: 'shortcut icon',
            type: 'image/x-icon'
        },
        js: [
            //List of your project's JS files goes here
            '/project/js/file.js'
        ],
        css: [
            //List of your project's CSS files goes here
            '/project/css/file.css'
        ]
    }
);

See demo/src/layout.html as an example.

License

(MIT License)

Copyright (c) 2016 Dima Snisarenko [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.