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

@trickle/mud.js

v1.3.2

Published

Mini UI-Build Dependence

Downloads

13

Readme

Introduction

You can learn about Mud.js more by ✨ 👉 Clicking 👈

Getting Started

# Install project builder
npm i @trickle/mud-cli -g

# Create a mud project
mud-cli create <name>

Development

When developing Mud.js, Here are some usual methods to make program execution result more intuitive:

Method 0

The most simple way is setting src of <script> to the entry file path, like this:

<script type="module" src="../src/index/js"></script>

Or do the same thing like this:

import Mud from '../src/index/js'

Method 1

Build the package and start a dev-server with rollup for hot module replacement:

npm run build:dev

Method 2

Use yalc to simulate publishing npm package:

npm i yalc -g

yalc publish

yalc add @trickle/mud.js

# Update the package
yalc push

Publish new version:

# Generate change-set file
npx changeset

# Update version
npx changeset version

Contributors

Thanks for all people mentioned below:

License

MIT