Mocking server supporting multiple route variants and mocks
npm install mocks-server-liteCredit: This is heavily inspired by mocks-server and takes some of the main concepts from it. It is massively simplified though, currently with only the core functionality as well as being TypeScript first. I created this because the mocks-server project doesnt currently seem to be very active and doesnt come with types and a few other features I think is key, which are listed below.
Node.js mock server that can run live, interactive mocks in place of real APIs. It allows you to define many different responses for a same route, so you can change the whole mocked API behavior by simply changing the response of one or many routes while the server is running. This really helps with local FrontEnd development when the BackEnd isnt ready/available and also really good for automated test runs where you want to change how the backing server behaves whilst it is still running.
- define multiple static or dynamic mock responses (variants) for api endpoints (routes)
- group together route mock responses in collections
- change route responses without having to restart the mocks server
- support route middleware
- add response delays with route override
- call logs so you can return something different on subsequent calls
- web sockets support
- static paths support
- What's the advantage of this over https://mswjs.io/?
No advantages per se but different in the fact youre actually calling a mocked server served at a URL rather than the request being intercepted at any level in code. Also different in that I don't see this as a mocking tool to use with jest or vitest, more to use with local development (if a BackEnd isnt ready/available) or supporting an E2E test run (using tools like cypress or playwright) where you dont want it hit a real BackEnd.
https://github.com/burt202/mocks-server-lite-example
- all mocking code is in mocks/, with the mock server being created in mocks/server.ts
- also see how the playwright test run can change the behaviour of the mocks server by caling setMockCollection which in turn calls POST /__set-collection with a new collection name