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

@brikcss/component

v0.3.2

Published

A scaffolding / starter repo for new brikcss components.

Downloads

17

Readme

Brikcss Component

npm (scoped) npm (scoped) Travis branch Travis branch Commitizen friendly semantic-release npm

A scaffolding / starter repo for brikcss components. Follow these steps to set up a new component.

  1. Set up the new component repo & test
  2. Update configs / root files
  3. Set up dependencies
  4. Create the component

Set up the new component repo & test

  • [ ] Clone (or fork) this repo.
  • [ ] Create repo in GitHub for new component.
  • [ ] Configure remote branch tracking as follows:
    • [ ] origin: tracks the new component repo in GitHub.
    • [ ] upstream: tracks this scaffolding repo.

Update configs / root files

  • [ ] .browsersync.js:
    • [ ] files property to watch build files.
    • [ ] server property to set the correct baseDir and index values.
    • [ ] Any other browsersync settings as desired.
  • [ ] .gitignore.
  • [ ] .travis.yml (scripts fields).
  • [ ] package.json:
    • [ ] All fields with "component" to the new component name.
    • [ ] description.
    • [ ] keywords.
    • [ ] main and module with the correct entry files.
    • [ ] release and publishConfig with the correct branch/dist-tags.
    • [ ] files with all files necessary for a release.
    • [ ] scripts:
      • [ ] prod:clean paths (and possibly add mkdirp to recreate dist dirs?).
      • [ ] js:watch and js:lint paths.
      • [ ] sass:watch and sass:lint and sass:dist paths.
      • [ ] If the component will have dist files, or if there are any tasks you want the release process to run prior to publishing, add the following NPM script to package.json:
        "prepublishOnly": "npm run prod"
    • [ ] devDependencies.
  • [ ] README.md:
    • [ ] Update shields to show data for the new component.
    • [ ] Update the rest of README.md as desired.
  • [ ] webpack.config.js to ensure it compiles the correct files / bundles.

Set up dependencies

  • [ ] Install NPM packages with npm install.
  • [ ] Set up semantic-release by running semantic-release-cli setup.

Note: Semantic release will publish your first release as version 1.0.0, there's no known way to change this. If you want to start at an earlier version (such as 0.0.1), do the following:

  • [ ] Update the version in package.json to 0.0.1.
  • [ ] Publish your first release manually with npm publish --tag=<tag> --access=public.
  • [ ] Update version in package.json back to 0.0.0-development.

Create the component

Directory structure:

  • src: Original source code.
  • examples: Code or test examples.
  • tests: UI and unit tests.
  • dist: Files for distribution (if any).
  • lib: Helper scripts (i.e., NPM scripts or git hooks).
  • docs: Documentation.