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

@contentmunch/muncher

v4.0.5

Published

Content editor wysiwyg

Downloads

46

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

contentmunchercontentmuncher

Keywords

html5reactjsuicomponent driven

Readme

Build release and publish

Muncher

Muncher is a rich text editor based on Lexical with a focus on content reuse.

Using Muncher

To use this component library:

  • add the npm package to your project
    $ npm install @contentmunch/muncher

Installation guide

In the project directory, you can run:

npm start

Launches the component explorer on port 6009

npm test

Launches the test runner in the interactive watch mode. See the section about running tests for more information.

npm run build

Builds the package library.

Coding rules

We use GitHub Flow for our project workflow. To ensure consistency throughout the source code, keep these rules in mind as you are working:

  • Create pull request against develop to merge your code.
  • All features or bug fixes must be tested by one or more [specs][unit-testing].

Pull request format

<subject>

* changes 1
* changes 2

fixes/closes #<github issue number>

Git commit format

<type>: <subject>
<BLANK LINE> 
<body> optional
  • Any line of the commit message cannot be longer 100 characters. This allows the message to be easier to read on GitHub as well as in various git tools.
  • The subject contains succinct description of the change:
    • use the imperative, present tense: "change" not "changed" nor "changes"
    • no dot (.) at the end
  • Commit type:
    • feat: a new feature
    • fix: a bug fix
    • refactor: a code change that neither fixes a bug nor adds a feature
    • test: adding missing tests
    • chore: changes to the build process or auxiliary tools and libraries such as documentation generation