Merge pull request #1441 from danielpeintner/issue-1430-typescript-eslint-no-empty-object-type

refactor: activate eslint @typescript-eslint/no-empty-object-type

Author: relu91

eslint.config.mjs

@@ -123,7 +123,7 @@ export default defineConfig([
             "@typescript-eslint/no-unused-expressions": "off",
             "@typescript-eslint/no-require-imports": "off", // https://github.com/eclipse-thingweb/node-wot/issues/1430
             "@typescript-eslint/prefer-nullish-coalescing": "error",
-            "@typescript-eslint/no-empty-object-type": "off", // https://github.com/eclipse-thingweb/node-wot/issues/1430
+            "@typescript-eslint/no-empty-object-type": "error",
             "@typescript-eslint/no-floating-promises": "off", // https://github.com/eclipse-thingweb/node-wot/issues/1430
 
             // ****************  Enforce usage of `const` over `let` wherever possible, to prevent accidental reassignments

packages/core/src/protocol-helpers.ts

@@ -26,7 +26,7 @@ export interface IManagedStream {
     wotStream: ReadableStream;
 }
 // eslint-disable-next-line @typescript-eslint/no-explicit-any
-function ManagedStream<TBase extends new (...args: any[]) => {}>(Base: TBase) {
+function ManagedStream<TBase extends new (...args: any[]) => object>(Base: TBase) {
     return class extends Base implements IManagedStream {
         _nodeStream?: Readable;
         _wotStream?: ReadableStream;