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

@muraldevkit/ds-semrel-stencil-exports

v1.0.1

Published

Semantic Release plugin for releasing Mural's design system's Stencil exports

Downloads

7

Readme

Mural design system Semantic Release Stencil exports plugin

We use Semantic Release for version management and the package release workflow. This package is a semantic-release plugin that manages the release process of a Stencil.js export target. Stencil exports have a separate package that don't have their own Semantic Release process. This plugin is in charge of publishing those packages to NPM.

Table of contents

  1. Setup
  2. Usage
  3. How it works

Setup

This plugin must be used only in the @muraldevkit/ds-semrel-config package by adding the plugin name to the plugins array.

const plugins = [
	'@semantic-release/release-notes-generator',
	'@muraldevkit/ds-semrel-stencil-exports'
];

No other configuration is required.

Usage

This plugin is part of our shared Semantic Release configuration. It will run on every Semantic Release pipeline, skipping its functionality if the package is not a Web Component.

At the moment only React components are supported.

To release a React component, create a package for it within the packages/react folder. It should be named @muraldevkit/ds-<component-name>-react in the package.json file.

For more information on how React exported components work please refer to our repository guides.

How it works

This plugin implements the following Semantic Release lifecycles:

| Step | Description | |--------------------|-------------| | verifyConditions | Verify if the package that runs Semantic Release is a Web Component. Check if the component has a valid React package. | | success | If the Web Component package is released successfully, it publishes the corresponding React package to NPM with the same version number. |

Different checks are performed during the verifyConditions step for a Web Component to ensure:

  1. It has a name that includes the component keyword (e.g., @muraldevkit/ds-component-button).
  2. It has a stencil.config.ts file.
  3. It has a matching React package that follows the naming convention @muraldevkit/ds-<component-name>-react.

If the above conditions are not met this plugin will output a log notifying the user that it will not release the React package. It does not affect the Web Component's release process.

Once the Web Component's release process reaches the success step, it will check that a nextRelease object exists within the Semantic Release context. If there is a nextRelease object, it will use the nextRelease.version number to update the React package version number.

After updating the React package version number it will publish that package to NPM using the npm publish command.