Describe the bug

A few of our services are split into a server and client version to deal with differences between NodeJS and the browser:

• CookieService
• AuthService
• HardRedirectService
• KlaroService
• AuthRequestService
• ReferrerService

Most of these services are abstract, and extended by Server* and Client* classes to define platform-specific behaviour.

Unexpected issues can occur when the abstract class itself imports or injects platform-specific code
For example, CookieService and AuthService leak Express imports into client code.

We've seen this break new services depending on CookieService & AuthService with cryptic errors like

An unhandled exception occurred: Debug Failure. False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature. This is probably not a problem in TS itself.

To Reproduce

N/A, mainly relevant when writing new code.

Expected behavior

Server and client logic should be split more cleanly.