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

blaze

v5.0.0-old

Published

Open Source UI Toolkit

Downloads

2,879

Readme

Please use separate @blaze packages

Blaze has moved to scoped packages under @blaze.

This makes it easier for you to install only what you need and allows us to name and organise our packages how we'd like.


Blaze

Blaze is a framework-free open source UI toolkit. It provides great structure for building websites quickly with a scalable and maintainable foundation.

https://www.blazeui.com

ci build status

Local Developer Setup

First of all install NVM.

When that is complete run:

$ nvm use
$ npm i

That's essentially it! Here are some useful commands:

| npm run <command> | Description | | ------------------- | :----------------------------------------------------------------- | | test | Lints all the scss files and runs all the tests on the atoms | | dev | Runs the dev servers with live reloads for both scss and atoms | | commit | To commit any changes please use npm run commit, more info below |

Committing

When committing changes please follow the Conventional Commits format.

The best thing to do is simply run npm run commit and it'll take you through a step-by-step wizard.

Installing the CSS

The easiest way to use the toolkit is via CDN.

<link rel="stylesheet" href="https://unpkg.com/@blaze/[email protected]/dist/blaze.css">

The x.x.x is the specific version of the library, you should use specifc versions to prevent against breaking changes.

How to start applying styles

We've designed the toolkit not to interfere with others or your own styles, hence Blaze won't automatically do anything to your site.

The following won't change by simply linking to blaze.css like it would with others such as Bootstrap or Foundation:

<button type="button">Button</button>

You need to apply our button classes:

<button class="c-button" type="button">Button</button>

This means you have to add classes to each part of your site where you want Blaze to apply. Take a look at the documentation for our objects, components, typography etc. and you'll see how intuitive it is to use.

Installing the JavaScript Components

Link to it by adding the following to your <head></head>.

<script src="https://unpkg.com/@blaze/[email protected]/dist/blaze-atoms.js"></script>

The x.x.x is the specific version of the library, you should use specifc versions to prevent against breaking changes.

That's it! Start using the components in your HTML.

Integrating with a Framework

Blaze uses Stencil to compile our components into Web Components. And since they can be used within frameworks or in standard HTML websites the best resource to read is the Stencil documentation regarding framework integration.