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

@gridonic/components

v0.2.1

Published

![Gridonic Components](./media/logo.png)<br><br><br>

Downloads

8

Readme

Gridonic Components

DRY

Don’t repeat yourself.

This is our components library. It mostly consists of Sass mixins, Vue components and Twig partials. They all are built with best practices in mind and common features we usually have to implement, but in a way we can adapt and customize them.

Sounds good? It is.

I want to contribute.

Noice. We like.

To get started you just have to clone it (git clone [email protected]:gridonic/components.git) and npm install it.

Now comes the fun part. If you want to add styles or Vue components, you can develop and test them with the included Storybook. Just run npm run storybook:serve and Storybook will automatically open your browser. Don’t know how to proceed? Head to the Storybook docs and familiarize yourself.

If you want to at Twig partials, feel free to do so. There is currently nothing set up for testing them.

How do I keep up with the extreme high quality of those components?

Ask your co-workers, Google, Stackoverflow or the linter of your trust. Or create a pull request if you want to be on the safe side.

Also make sure to write tests. Please for the love of god, do it. Just run npm run test to test your tests.

Publishing

When ready to release, execute the following steps, given that all changes are commited in the master branch:

  • List changes in the CHANGELOG.md
  • Bump your version and automatically create a git tag with npm version <type>, where type is patch, minor or major
  • Push the master branch git push and the tags git push --tags
  • Create a release in github and fill the description with at least a link to the CHANGELOG.md. Add more information if necessary

That's it! A github action will then automatically publish the package to npm.