Class BaseServerExtensionAbstract

Abstract base class for MJServer extensions.

Extensions are discovered via @RegisterClass(BaseServerExtension, 'DriverClassName') and matched to config entries in mj.config.cjs by their DriverClass name.

MJServer calls Initialize() during startup, passing the Express app so the extension can register its own routes, middleware, and lifecycle hooks.

Lifecycle

1. MJServer reads serverExtensions[] from mj.config.cjs
2. For each enabled entry, looks up @RegisterClass(BaseServerExtension, driverClass)
3. Creates instance via ClassFactory.CreateInstance()
4. Calls Initialize(app, config) — extension registers routes
5. Periodic HealthCheck() calls for monitoring
6. On server shutdown, calls Shutdown() for cleanup

Usage

import { RegisterClass } from '@memberjunction/global';
import { BaseServerExtension, ServerExtensionConfig, ExtensionInitResult } from '@memberjunction/server-extensions-core';

@RegisterClass(BaseServerExtension, 'MyCustomExtension')
export class MyCustomExtension extends BaseServerExtension {
    async Initialize(app: Application, config: ServerExtensionConfig): Promise<ExtensionInitResult> {
        app.get(config.RootPath + '/hello', (_req, res) => {
            res.json({ message: 'Hello from my extension!' });
        });
        return { Success: true, Message: 'Custom extension loaded', RegisteredRoutes: [`GET ${config.RootPath}/hello`] };
    }

    async Shutdown(): Promise<void> {
        // Clean up resources
    }

    async HealthCheck(): Promise<ExtensionHealthResult> {
        return { Healthy: true, Name: 'MyCustomExtension' };
    }
}
Copy

Auth Middleware

Extensions handle their own authentication by default. If you want to leverage MJServer's built-in auth middleware, import it from @memberjunction/server:

import { getSystemUser, verifyUserRecord } from '@memberjunction/server';
Copy

This is opt-in — extensions like Slack/Teams use platform-specific auth (signature verification, Bot Framework JWT) instead.