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

@dynamic-framework/dynamic-commons-base-template

v1.4.0

Published

## Requirements: - node@20+ - npm@10+

Downloads

145

Readme

dynamic-commons-base-template

Requirements:

  • node@20+
  • npm@10+

Setup

  1. Change the property name in package.json to the name of your commons.

[!IMPORTANT]
Remember to use the scope of your organization. 2. Change the scope in the actions/setup-node@v4 step of .github/workflows/release-please.yml to the scope of your organization.

  1. Workflow permissions
    • If in your repository the actions in workflow permissions don't have permission to create and approve pull request, create a PAT token with the permissions repo, workflows and write packages and add it as a repository secret with the name RELEASE_PLEASE_TOKEN.
    • If in your repository the actions in workflow permissions have permission to create and approve pull request, change in .github/workflows/release-please.yml ${{ secrets.RELEASE_PLEASE_TOKEN }} to ${{ secrets.GITHUB_TOKEN }}
  2. To apply the client theme in the storybook change in .storybook/preview-head.html the link <link rel="stylesheet" href="https://www.unpkg.com/@dynamic-framework/ui-react@latest/dist/css/dynamic-ui-root.min.css" /> to a link to the theme css in the platform.

Usage

The best way to use this template is to create a repository from it on GitHub.

npm install @your-scope/your-package-name

or if you want to test our template

npm install @dynamic-framework/dynamic-commons-base-template

[!IMPORTANT]
Remember that commons includes the framework as a peer dependency, you must install the framework in your widget

Learn More

Find more information about microfrontends and configuration details on Modyo Docs & Modyo Community