Fixes for TS type issues introduced in [email protected] / TS 5.5

[ericyhwang]

[email protected] introduced a handful of TypeScript errors when used with Derby.

Fix Derby app.use(plugin, options) TS error

When registering a Derby app plugin with strict types, [email protected] introduced errors like this:

Argument of type '(app: App, appName: string) => void' is not assignable to parameter of type '(arg0: unknown, options?: unknown) => void'.
  Types of parameters 'app' and 'arg0' are incompatible.
    Type 'unknown' is not assignable to type 'App'.

Derby utilizes the plugin use function from Racer, which in [email protected] switched the plugin function from implicit anys to explicit unknowns.

This changes the use function to use inferred generic types, which allows proper verification that the plugin uses the correct options and this if specified.

TS 5.5 related updates

Updates to have Racer work properly with TS 5.5:

• The triple-slash reference directives used to load types for server-only model methods are no longer automatically included in the output d.ts files.
  • This was causing TS errors like Property 'createConnection' does not exist on type 'RootModel'. in Derby.
  • We need to add preserve="true" to tell the compiler to include them.
• Remove noImplicitUseStrict compiler flag, since TS 5.5 no longer supports it
  • This means the output JS files with each have a "use strict"; at the top
• Update typedoc deps for TS 5.5 compatibility

The TypeScript dependency was using ^5.1, which was automatically picking up new major TypeScript versions. TS doesn't use semver, and each +0.1 is treated as a major version.

This switches to using a ~ dependency so Racer wont pick up major TS releases automatically.