[Bug]: 10.0.0 types inferred as `any` break compilation

[agross]

I'm sure that

• This issue is still present in the current beta version of this adapter
• There is no other (open) issue with the same topic (use the search!)
• This issue is not described in the adapter documentation / FAQ (read the docs!)

Script type

TypeScript

The problem

My scripts heavily rely on rxjs. I need to use rxjs 6.x because newer versions don't work with ioBroker.javascript.

ioBroker.javascript 9.3.1 with rxjs@6 installed works fine with this piece of simplistic code:

import { Observable } from 'rxjs';

new Observable<string>(observer => { })

The code compiles and runs, despite the observer type not being inferred.

Not an issue for me because I write my scripts in VS Code:

With ioBroker.javascript 10, the same code no longer compiles:

TypeScript compilation failed:
new Observable<string>(observer => { });
                       ^
ERROR: Parameter 'observer' implicitly has an 'any' type.

With explicit types, compilation does succeed (VS Code accepts it too, so does tsc):

import { Observable, Subscriber } from 'rxjs';

new Observable<string>((observer: Subscriber<string>) => {});

Why does type inference no longer work and now cause compiler errors?

iobroker.current.log (in debug mode!)

No response

Version of nodejs

22.22

Version of ioBroker js-controller

7.2.2

Version of adapter

10.0.0

[agross]

I ran Codex on this:

---

Cause confirmed: TypeScript 6 default change, not rxjs regression.

• v10 upgraded TypeScript 5.9.3 → 6.0.3 in package.json:57, via PR Typescript6 #2335.
• TypeScript 6 enables strict by default. This implicitly enables noImplicitAny. Official TypeScript 6 notes.
• Adapter compiler options in src/lib/typescriptSettings.ts:7 set neither strict nor noImplicitAny.
• Live runtime confirmed effective values: strict=true, noImplicitAny=true.
• rxjs inference was already failing under v9—the editor displayed observer: any. v9 tolerated it because strict mode defaulted off. v10 rejects same existing any.

Live reproduction produced TS7006. Adding strict: false made TS7006 disappear. Original test script restored and running.

Compatibility fix: explicitly add strict: false to tsCompilerOptions. Narrower fix: noImplicitAny: false, but other newly enabled strict checks would remain. No repository files changed.

---

I prefer a fix to get type inference working.

[agross]

I have the necessary changes required to fix my scripts in my fork:

master...agross:ioBroker.javascript:issue-2341

In the long term, I'd rather fix #928 and think about how to implement global scripts, regular scripts, and additional node_modules with default TypeScript compilation. Please share your thoughts.

[technyon]

Wouldn't it make sense to make this user configurable. strict can be enabled by default, but should be easy to disable. I have a lot of scripts to fix, which I use not only for me but also for friends and family. It would be a lot of work to go through all of that.