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

muenchhausen

v1.0.8

Published

Produce authentic mockup fake data

Downloads

64

Readme

MUENCHHAUSEN Muenchhausen Logo

NPM version Build Status Dependency Status Coverage percentage Codacy BadgeDonate

Make your test data look real. In Node and in Browser

Installation

npm install --save muenchhausen

Usage

Muenchhausen expects a culture string as parameter like "de-DE" or "en-GB". All available cultures are listed in cultures.json

var Muenchhausen = require("muenchhausen");
var muenchhausen = new Muenchhausen("de-DE");

Render

var muenchhausen = new Muenchhausen("en-GB");
var news = muenchhausen.render("$(date.now.text) - $(date.random.value min:20200901)  $(date.random)");
console.log(news);

/*
yields => 13/05/2017 - Thu Jul 14 8416 12:51:52 GMT+0200 (Mitteleuropäische Sommerzeit)  06/00/2784
*/

Programmatically

var muenchhausen = new Muenchhausen("ja-JP");
console.log(muenchhausen.fake.date.now({}).text());
console.log(muenchhausen.fake.date.weekday().text());

/*
yields =>
2017/02/22
金曜日
*/

Benchmarks

/docs/BENCHMARK.md

Client

A shell client is avialable at muenchhausen-client.

API

/docs/

Contribute

Please read /CONTRIBUTING.md for details.

Write your own extension

fake/random is a pretty simple starting point to see how a muenchhausen extension works.

In generall it contains a simple node module. Methods prefixed with _ are private. Unprefixed funtions are available in the public render method and will be scanned while the module unit tests. Each unprefixed function have to return an object with the property value and a function called text.

  • [x] .text() should optionaly process given parms and render a text representation of .value.
  • [x] .value should hold the native JavaScript value (if possible).

Nice to have

  • [x] new unit test(s).
    • [ ] write unit tests and run npm test or mocha for faster results.
  • [x] new benchmark(s).
    • [ ] write a benchmark or more and run npm run benchmark which will update BENCHMARK.md.
  • [x] new doc(s).
    • [ ] Add jsdox descptions to your public function headers and npm run docs will update /docs folder.
  • [x] Error and code coverage test.
    • [ ] run npm test to start gulp taks. Fix eslint error and check your code coverage described in muenchhausen/coverage/lcov-report/index.html.

License

MIT © s-a