Stubby4node Versions Save

A configurable server for mocking/stubbing external systems during development.

5.1.0

3 years ago
  • You can now submit DELETE / to the admin endpoint to delete all configured stubbed endpoints (#89)

5.0.0

3 years ago
  • BREAKING CHANGES from 4.x
    • The exit code for the stubby bin script will reflect the expected/error state of stubby.
  • Dependencies have been updated to prevent vulnerabilities.
    • acorn updated from 7.0.0 to 7.1.1
    • updated node versions for testing
    • lodash updated from 4.17.15 to 4.17.19

4.1.1

3 years ago
  • Updates dependencies with reported vulnerabilities

4.1.0

5 years ago
  • Adds support for POST forms as a hashmap
  • Updates dependencies that had vulnerabilities

4.0.0

5 years ago

This project has been stable for some time, best we move to actual semver and not prerelease versioning. This release on the old versioning system would have been release 0.4.0. It is now 4.0.0 instead.

  • BREAKING CHANGES from 0.3.x

    • The mute option has been renamed quiet to be more consistent with other cli tools
  • New features

    • Adds hits to the endpoint data that is returned from the admin portal that represents the amount of times that endpoint has been hit from the stubs portal.

0.3.1

7 years ago
  • Fixes path errors in Node 6

0.3.0

8 years ago

BREAKING CHANGES from 0.2.x

In 0.2.x and below, you could pass request.headers.authorization as a username:password string to signify Basic auth and stubby would automatically prefix Basic and base64-encode the user/pass string. This breaks other forms of web auth that uses the Authorization header.

  # Before
  request:
    headers:
      authorization: 'username:password'
  # Now
  request:
    headers:
      authorization: 'Basic username:password'

Stubby will still base64-encode the username:password if it sees that Basic is specified and the : character is present. Otherwise it will take it as-is.

New features

json: option for endpoints -- instead of using post: or file: for matching the body of incoming requests, you can specify json: with a JSON string and its content will be deeply matched for incoming request bodies.

0.2.13

8 years ago
  • fixes a crash when using start() without any options

0.2.12

8 years ago
  • fixes array representations in query strings

0.2.11

8 years ago
  • fixes several scope-binding issues caused by the JavaScript rewrite (sorry!)
  • clarify use of PUT and the admin portal
  • added _httpsOptions to pass through options to the underlying tls server.