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

@mrshmllw/smores-react

v10.3.0

Published

Collection of React components used by Marshmallow Technology

Downloads

3,015

Readme

Smores React

smores-react is a collection of React components that conform to Marshmallow's Design System - "S'mores".

Install

$ yarn add @mrshmllw/smores-react
# OR
$ npm install @mrshmllw/smores-react

Making changes

When making changes and creating PR's we use semantic-releases which make use of conventional-commits.

So to ensure our CHANGELOG.md is updated automatically and gets the changes we have made, we just need to name our PR's following this convention (casing matters): e.g

  1. patch - fix(OPTIONAL bugfix-reference): some bugfix
  2. minor - feat(OPTIONAL feature-reference): some feature
  3. major - BREAKING CHANGE: some breaking change

Release

Only the following branches are supported for release:

  • main
  • feature/*
  • chore/*
  • fix/*

Preview

Before releasing, you may want to see the changes that will be included in the next version deployed on NPM, you can do so by:

  1. Goto our github workflows
  2. Click Preview Bump and Publish
  3. Press Run workflow and select the main branch.
  4. Wait for the Generate preview CHANGELOG.md and look at the results!

Releasing & Publishing

When you're happy with your changes, you can release & publish your changes to NPM in one fell swoop by:

  1. Goto our github workflows
  2. Click Bump and Publish
  3. Press Run workflow and select the main branch.
  4. Wait for release!

Note: this workflow will fail if the package version is already on the latest, so you dont have to worry about deploying the same changes multiple times.

Pre-Releases

Not too different to your usual workflow!

  1. Checkout a new branch with the prefix (feature|chore|fix)/<your-branch-name> e.g. feature/awesome-new-feature
  2. Open a PR and create your changes as normal using semantic-commits!
  3. Goto our github workflows
  4. Click Bump and Publish or Preview Bump and Publish
  5. Press Run workflow and select <your-full-branch-name> branch.
  6. Wait for release!
  7. This can be done multiple times and it will increment your pre-release package version!
  8. When you're happy with the changes, simply squash and merge the PR and release main!
Tokens

The MARSHMALLOW_CI_PAT has been created from the internal @marshmallow-ci GH account, it is due to expire on 27th November 2024 so will need regenerating once it does.

Running Smores in dev mode

To run Smores in dev mode follow the below instructions on installing and using Yalc to link up your project repo with Smores.

Install yalc on a global level by running

npm i yalc -g

This only needs to be installed once.

To run Smores in dev mode :

  1. Make desired changes in Smores repo
  2. On your Smores branch run
yalc publish

This will copy all the files that should be published into a remote NPM registry

In your project repo (not Smores e.g customer portal/sign up flow etc) run

yalc add @mrshmllw/smores-react

this will copy the current version from the store to your project’s .yalc folder and inject a file: .yalc/@mrshmllw/smores-react dependency into package.json

Every time you make changes in Smores and you wan’t to see it in local

run

yalc publish —private

In your project folder to see your Smores changes run the below to see the changes

yalc update

When you’ve finished deving run the below in your project folder to remove all packages linked

yalc remove --all

List of Components

Usage

import React from 'react';
import {Text, Button} from '@mrshmllw/smores-react';

const App = () => (
  <>
    <Text>Hey you</Text>
    <Button
      onClick={() => console.log('thanks for clicking :)')}
    >
      Click me!
    </Button>
  </>
);

License

MIT © Marshmallow