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

raml-1-mockup

v0.5.0

Published

Express-based mocking service for RAML development

Downloads

8

Readme

RAML Mock-ups!

Fork of the https://github.com/gextech/raml-mockup repo.

Original repo mostly relies on RAML 0.8 schema definitions, not on 1.0 types. The goal of this project is to implement better support for 1.0 features, types in particular. It uses type examples as mocking data.

Features

  • Uses json-schema-faker for accurate mocked responses (for 0.8 schemas).
  • Uses refaker for resolving remote/local $refs (for 0.8 schemas).
  • It's fully tested and coveraged.
  • Has watch mode built-in.

Improvements in comparison to the original fork

  • Supports all content types, not only application/json
  • Uses Type examples for mocking (if resource-level example is not defined)
  • Readme tweaks

How to setup & use

Install raml-1-mockup globally:

$ npm install -g raml-1-mockup

Then starts a mock-server from your RAML:

$ raml-1-mockup src/api.raml -p 5000 -w

Now you can make requests through the mocked-API:

$ http http://localhost:5000/path/to/resource

The better if you're using httpie.

Options

General

  • --timeout → Timeout requests from remote dereferencing.
  • --silent → Turns off the reporting through the STDOUT.
  • --watch → Enables the watch mode for mock-server.
  • --port → Custom port for mock-server.
  • --statuses → Use custom statusCode(s) for all matched resources.

Mocking for 0.8 schema definitions

  • --directory → Used with --fakeroot to resolve faked references through this directory.
  • --fakeroot → BaseURI for references that will fake (i.e. http://json-schema.org).
  • --formats → CommonJS module-id or path for custom formats.

Run raml-1-mockup -h to display all usage info.

queryParams

Use the following options for custom responses:

  • _statusCode=200 → Force a specific statusCode if its available.
  • _forceExample=true → Force defined resource-example if its available.

Issues?

Please open a ticket or feel free for contributing.

Development

Install jasmine-node:

$ npm install -g jasmine-node