jest-extended VS server

I recently came across a workaround for this issue by using the expect.toBeOneOf() matcher from the jest-extended library. This matcher allows you to check whether a value matches one of the expected values, including null and undefined.

Yes, a standardized expect would be nice, but care has to be taken to not bloat it.

Currently I use vitest and https://github.com/jest-community/jest-extended which gets you a reasonable amount of usable matchers.

Jest-Extended: Additional Jest matchers

I created Server.js https://serverjs.io/ and still use it. It is a wrapper around express:

- With a bunch of middleware included and pre-configured, like body-parser, cookies, Helmet, etc. All express middleware works with Server.js

- async/await routers as expected: get('/users', async (ctx) => {...}); (ctx inspired by Koa)

- Websockets, where messages behave just as another route: socket('message', async ctx => { ... });

I did that! I hope you are not the person who suffered that from me (did you use Picnic CSS a few years back?). So for a newer project I put some setup code that will look for all code snippets with a specific comment and run that with the code after the comment. For generating the website documentation that test bit can be stripped (though I kept it for now).

Example: https://github.com/franciscop/server/blob/master/docs/docume...