Nicolas

### Intended behavior NA ### Solution Update to the v1, impacts: - change scss file, - need to reduce css generated witth postCss - check if no legacy components (tiles)...

fix(content-type): Fastify v5 parser leads to HTTP 415

4

Fix fox1t/fastify-multer#35

Fastify v5 fails with HTTP 415 FST_ERR_CTP_INVALID_MEDIA_TYPE

1

When I upgrade from Fastify v4.28 to 5.2, uploads of multipart/form-data failed with a 415 HTTP: ``` json { "code": "FST_ERR_CTP_INVALID_MEDIA_TYPE", "name": "FastifyError", "statusCode": 415, "message": "Unsupported Media Type: multipart/form-data;...

feat(ws): allows to choose which messages are handled

1

Hello, it is me again 😉 Here a proposal for allowing user to choose which message received from the websocket will be handled: 

Hello, After modifying the WS node (the Unifi url, for example) and redeploying, messages are sent twice, as we use the [`wslogin` function with a timeout](https://github.com/Isaksson/node-red-contrib-unifi/blob/master/unifi.js#L404-L407). ```js node.tout = setTimeout(function...

feat: allow multiple calls in parallel

1

Hello, I propose this PR to allow multiple calls in parallel (in case using split/join nodes). I've also slightly modified the code to allow a call without a payload.

PHP code is complex to maintain. Migration to a Fastify server should allow further evolution.

Some nodes does not trigger `onComplete` hook

3

### Current Behavior Some nodes like `http in` or `tcp in` does not trigger `onComplete` [hook](https://nodered.org/docs/api/hooks/messaging/#oncomplete). ### Expected Behavior All nodes should emit an `onComplete` event when they are completed....