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

hariko

v1.2.1

Published

Mock Server that implements the API Blueprint specification.

Downloads

8

Readme

node-hariko

Mock Server that implements the API Blueprint specification.

npm version Build Status Code Climate Test Coverage

Get started

Installation

npm install -g hariko

Usage

hariko\
  -f <glob expression to your md files>\
  -p <server port>

Examples

for CLI

hariko -f 'docs/**/*.md' -p 8080 -w

for Node.js

var hariko = require('hariko')
hariko.start(
  {
    file: 'docs/**/*.md',
    watch: true
  },
  function() {
    console.log('Starting hariko server.')
  }
)

CLI Options

file

Filename in the node-glob format of API Blueprint.

hariko -f 'docs/**/*.md'

exclude

Exclude filename in the node-glob format.

hariko -f 'docs/**/*.md'\
       --exclude 'docs/metadata.md'\
       --exclude 'docs/overview.md'

port

Port number of API Server. By default 3000.

hariko -f 'docs/**/*.md' -p 8000

host

Hostname of API Server. By default localhost

hariko -f 'docs/**/*.md' --host '0.0.0.0'

watch

Watching changes for markdown files. By default false.

hariko -f 'docs/**/*.md' -w

This watch we have been using the gaze. If you want to exit the watch is, enter Ctrl + C.

output

Output in the form of HarikoReosurce to JSON.

hariko -f 'docs/**/*.md' -o 'api/'

When output option is enabled, the server can perform realtime data changes because reading JSON.

proxy

A origin for proxy request. By default false.

hariko -f 'docs/**/*.md' --proxy 'http://localhost:8100'

verbose

Output the verbose log. By default false.

hariko -f 'docs/**/*.md' -v

CORS

Send CORS header. By default false.

hariko -f 'docs/**/*.md' --cors

log-level

set to log level.

hariko -f 'docs/**/*.md' --log-level debug

time

Output the logging time. By default false.

hariko -f 'docs/**/*.md' -t

API

var hariko = require('hariko')

hariko.start(options [, startCalleback]);

hariko.start({ file: 'docs/**/*.md' }, function() {
  console.log('hariko started!')
})

Development

run build

> ./docker-dev/bin/build
> docker run --rm -it -v$(pwd):/usr/local/docker/app --name hariko hariko npm run build

run tests

> ./docker-dev/bin/build
> docker run --rm -it --name hariko hariko npm test

License

MIT