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 🙏

© 2025 – Pkg Stats / Ryan Hefner

tyshemo-service

v3.0.7

Published

TYSHEMO SERVICE ===============

Readme

TYSHEMO SERVICE

This package is based on TySheMo. It can help you to serve up a doc server, a mock server and a testing server quickly with your types files.

Install

npm i tyshemo-service

Usage

const Service = require('tyshemo-service')
const server = new Service(options, configs)

server.mock() // serve up a mocker server
// server.doc() // serve up a doc server

Options

{
  // required
  data: [],

  // optionals
  base: string, // api base url
  error: {
    code: 'error_code',
    error: 'error_message',
  },
  errorMapping: mapping, // mapping for error code and messages
}

errorMapping

{
  10001: 'database disconnected.',
}

data

To serve up, the most important information to pick from.

data: [ // group level, to group apis and show tree in doc
  {
    name: 'group name',
    items: [ // api item level
      {
        name: 'api name',
        description: 'api description',
        method: 'get', // lowercase, will be used by express to route
        path: '/path/:id', // concat with basePath, will be used by express to serve up mock server, show in doc page

        request: {}, // json
        response: {}, // json

        // override global options
        base: '',
        error: {}

        // unit test
        test: [
          {
            frequency: 1000,
            // unit name
            name: '111',
            // replace params in `path`
            params: {
              id: '123',
            },
            // override request mocking
            request: {},
          }
        ],

        // override response mock data
        mock: {
          // use keyPath to override
          'data.body.some': 123,
        },
      },
    ],
  }
]

The most important is request and response options. The Type instances should be imported from which is shared with your project code.

Configs

const Service = require('tyshemo-service')
const server = new Service(options, configs)

server.mock(customMockConfig)
server.doc(customDocConfig)
server.test(customTestingConfig)
server.serve()

configs

{
  port: number, // used when invoke server.serve()
  // used when only invoke server.doc()
  doc?: {
    port: number,
    title: string, // used when invoke server.serve()
    description: string, // used when invoke server.serve()
    template: FileAbsPath, // used when invoke server.serve()
    root: string, // the root uri to visit default '/' // used when invoke server.serve()
  },
  // used when only invoke server.mock()
  mock?: {
    port: number,
    transformer: function, // you can modify mock data before it out // used when invoke server.serve()
  },
  // used when only invoke server.test()
  test?: {
    port: number,
    target: 'http://my.api.com', // the target api host to test // used when invoke server.serve()
    title: string, // used when invoke server.serve()
    description: string, // used when invoke server.serve()
    root: string, // defualt '/', '/_test' when serve // used when invoke server.serve()
    template: FileAbsPath, // used when invoke server.serve()
  },
}

When you invoke server.doc() or server.mock(), you can pass server config into these methods.

When you invoke server.serve(), the ports of doc, mock, test will not work

template

The docTemplateFile and testTemplateFile give your the ability to modify want you see in browser. You should look into doc.html and test.html.

The placeholder string __TITLE__ __DESCRIPTION__ and __DATA__ can be used in your template.