Alex Bolshakov

https://typia.io/docs/json/stringify/ performance claims are at least misleading

3

a) Every single benchmark result demonstrates clear superiority of `typia.stringify()` over `JSON.stringify()` while its only true for small payloads. Please add benchmarks for larger payloads. b) Unlike https://www.npmjs.com/package/fast-json-stringify, your website...

[Feature request] API SDK extraction

2

# Problem We all love type-safe interaction between system components. It's also a great idea to be able to use the same TypeScript types both in our server and client...

Feature request: DX: Logger: Scopped logger autoinjection

1

.NET-alike generic logger autoinjection: ```ts export class SessionsService { constructor( protected readonly logger: Logger // results in logger.scoped('SessionsService') autoinjection ) } ```

DI: Module provider visibility issue

7

I've created a PR with a failing test case: https://github.com/deepkit/deepkit-framework/pull/595/files#diff-8638469975c860d179cea016ca3ee1f3c2d65fbd6eba97a2096def06beeaa332R193 TL;DR is provider registered within a deeply nested module isn't available for ingestion within the same module, unless this module...

### Relinquishment of Rights Please mark following checkbox to confirm that you relinquish all rights of your changes: - [x] I waive and relinquish all rights regarding this changes (including...

HTTP: compression should not be enabled by default

1

The worst task JS could do is compression. It's usually better handled by ingress servers such as Nginx, Caddy or Traefik. I would ditch compression from the framework completely or...

DX: Bug?: HTTP: better `next()` usage docs

2

It's currently stated at [documentation](https://deepkit.io/documentation/http/middleware): > All middleware needs to execute next() sooner or later. If a middleware does not execute next() withing a timeout, a warning is logged and...

Consider the following middleware: ```ts import { HttpMiddleware, HttpRequest, HttpResponse } from '@deepkit/http'; export class AuthenticationMiddleware implements HttpMiddleware { constructor() {} async execute( request: HttpRequest, response: HttpResponse, next: (err?: unknown)...

Throwing or passing `next()` an error (even `HttpError`) results in weird behavior: Expected result would be no `Could not resolve request` thing with 404 response code, but rather 403 response...

One have to always write `createModule({})` instead of just `createModule()`