@primexop/pbk/dist/index.js

Primexop Backend Kit - A powerful TypeScript utility for managing backend projects with features like B2F Portal integration, cross-project validation, and Next.js support

/**
 * Main entry point for the package
 */
import * as path from 'path';
import { b2fPortalInit } from './b2fPortalV3/b2fPortal.js';
import { checkCrossProjectImportsFun } from './helpers/checkCrossProjectImports.js';
import { loadConfig } from './utils/loadConfig.js';
export function greet(name) {
    return `Hello, ${name}!`;
}
/**
 * Initializes the pbk by loading configuration from a JSON file.
 * This is the primary initialization method for the library.
 *
 * @param {Object} options - Initialization options
 * @param {string} [options.configPath] - Path to the JSON config file (defaults to pbk.config.json in current directory)
 * @returns {TPbkConfig} The loaded and validated configuration
 * @throws {Error} If the configuration is invalid or file doesn't exist
 */
export async function pbkInit(options = {}) {
    // Set default options
    const { configPath = path.join(process.cwd(), 'pbk.config.json') } = options;
    try {
        // Load and validate config
        const config = loadConfig(configPath);
        if (!config) {
            return {};
        }
        console.log(`Successfully loaded configuration with ${config.projects.length} projects`);
        // Initialize features based on config flags
        if (config.b2fPortal) {
            await b2fPortalInit(config.projects);
        }
        if (config.checkCrossProjectImports) {
            await checkCrossProjectImportsFun(config.projects);
        }
        return config;
    }
    catch (error) {
        console.error('Failed to initialize pbk:', error);
        throw error;
    }
}
// When using ES modules with TypeScript, you need to include the .js extension
// in import statements, even though the source file has a .ts extension
// This is because Node.js will look for .js files at runtime
export * from './types.js';