Nils Kuhnhenn

As a workaround you can hack in your own logic that disconnects clients and prevents new connections before initiating application shutdown.

Here's a workaround: ```ts // FIXME: workaround for https://github.com/nestjs/nest/issues/13910 if (forceCloseConnections) { const server = (app as NestExpressApplication).getHttpServer(); server.close = (close => (cb) => { close(cb); server.closeAllConnections(); return server; })(server.close.bind(server));...

I think a fix for this is to never call ``SocketIOServer.close()``, and instead track connections ourselves in the websocket adapter, destroy them on close, and also destroy any new incoming...

I have this same issue. I'm trying to dynamically generate navigation items from routes, for which I need to list all configured child routes of my lazy loaded module.

@mhevery I believe that at least three other use-cases are listed in this thread. Unless I'm missing something could you re-open this?

For ergonomics of that API it would also be nice if Shader was generic so the uniform groups properties on it can be typed (similar to how ``UniformGroup`` works).

Just tried this. Currently the inferred types are not correct. For a shader created with: ```ts function makeShader(seed: number, radius: number, baseColor: [number, number, number]) { return new Shader({ glProgram:...

That works! 👍