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

@emulsify/core

v2.4.2

Published

Bundled tooling for Storybook development + Webpack Build

Downloads

2,003

Readme

Emulsify Core Design System

Emulsify Core

An open-source toolset for creating and implementing design systems.

Emulsify Core provides a Storybook component library and a Webpack development environment. It is meant to make project setup and ongoing development easier by bundling all necessary configuration and providing it as an extendable package for your theme or standalone project.

Installation and usage

Installation and configuration is setup by the provided base theme project(s). As of this writing, Emulsify Drupal is the only base theme project with this integration.

Manual installation

  • npm install @emulsify/core within your repository or project theme.
  • Copy the provided npm run scripts from Emulsify Drupal's package.json
  • Copy the contents of whisk/config/emulsify-core/ from Emulsify Drupal into your project so config/ exists at the root of your repository or project theme. The files within config/ allow you to extend or overwrite configuration provided by Emulsify Core.

Common Scripts

Run nvm use prior to running any of the following commands to verify you are using Node 20. (Each is prefixed with npm run )

develop Starts and instance of storybook, watches for any files changes, recompiles CSS/JS, and live reloads storybook assets.

lint Lints all JS/SCSS within your components and reports any violations.

lint-fix Automatically fixes any simple violations.

prettier Outputs any code formatting violations.

prettier-fix Automatically fixes any simple code formatting violations.

storybook-build Builds a static output of the storybook instance.

Quick Links

Demo

  1. Storybook

Contributing

Code of Conduct

The project maintainers have adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.

Contribution Guide

Please also follow the issue template and pull request templates provided. See below for the correct places to post issues:

  1. Emulsify Drupal
  2. Emulsify Twig Extensions
  3. Emulsify Tools (Drupal module)

Committing Changes

To facilitate automatic semantic release versioning, we utilize the Conventional Changelog standard through Commitizen. Follow these steps when commiting your work to ensure semantic release can version correctly.

  1. Stage your changes, ensuring they encompass exactly what you wish to change, no more.
  2. Run the commit script via yarn commit or npm run commit and follow the prompts to craft the perfect commit message.
  3. Your commit message will be used to create the changelog for the next version that includes that commit.

Author

Emulsify® is a product of Four Kitchens.

Contributors