Skip to content

Releases: mrak/stubby4node

5.1.0

25 Mar 05:34
Compare
Choose a tag to compare
  • You can now submit DELETE / to the admin endpoint to delete all configured stubbed endpoints (#89)

5.0.0

17 Mar 02:10
Compare
Choose a tag to compare
  • 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

17 Mar 02:10
Compare
Choose a tag to compare
  • Updates dependencies with reported vulnerabilities

4.1.0

16 Mar 00:48
Compare
Choose a tag to compare
  • Adds support for POST forms as a hashmap
  • Updates dependencies that had vulnerabilities

4.0.0

16 Mar 00:48
Compare
Choose a tag to compare

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

27 May 15:48
Compare
Choose a tag to compare
  • Fixes path errors in Node 6

0.3.0

18 Mar 17:24
Compare
Choose a tag to compare

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

29 Sep 04:50
Compare
Choose a tag to compare
  • fixes a crash when using start() without any options

0.2.12

26 Sep 18:50
Compare
Choose a tag to compare
  • fixes array representations in query strings

0.2.11

26 Sep 18:50
Compare
Choose a tag to compare
  • 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.