@remotex-labs/xbuild 1.5.9 → 1.5.11

package/dist/cli.d.ts

@@ -1,11 +1,106 @@
+
+/**
+ * This file was automatically generated by xBuild.
+ * DO NOT EDIT MANUALLY.
+ */
+ import type { SourceService } from '@remotex-labs/xmap';
+import { SourceService } from '@remotex-labs/xmap';
+export type { BuildResult, OnLoadArgs, OnLoadResult, OnResolveArgs, OnResolveResult, PluginBuild } from 'esbuild';
+import type { BuildResult } from 'esbuild';
+import type { BuildOptions } from 'esbuild';
+import type { IncomingMessage, ServerResponse } from 'http';
+import type { Loader, OnLoadArgs, BuildResult, OnEndResult, PluginBuild, OnLoadResult, OnResolveArgs, OnResolveResult } from 'esbuild';
+import type { Format } from 'esbuild';
+import type { Argv } from 'yargs';
+import type { ChildProcessWithoutNullStreams } from 'child_process';
+import type { Loader, Metafile, OnLoadArgs, OnLoadResult } from 'esbuild';
+import type { BuildOptions, BuildResult, Metafile } from 'esbuild';
+import type { Message } from 'esbuild';
+import type { Plugin } from 'esbuild';
+import type { ParsedCommandLine, Diagnostic } from 'typescript';
+import type { OutputFile } from 'typescript';
+import type { FormatDiagnosticsHost } from 'typescript';
+import type { CompilerOptions, IScriptSnapshot } from 'typescript';
+import type { ParsedCommandLine, LanguageService } from 'typescript';
+import type { Context } from 'vm';
+
 #!/usr/bin/env node
-import type { SourceService } from "@remotex-labs/xmap";
-import type { Loader, OnLoadArgs, BuildResult, OnEndResult, PluginBuild, OnLoadResult, OnResolveArgs, OnResolveResult, BuildOptions, Format, Metafile, Message, Plugin } from "esbuild";
-import type { IncomingMessage, ServerResponse } from "http";
-import type { Argv } from "yargs";
-import type { ChildProcessWithoutNullStreams } from "child_process";
-import type { OutputFile, FormatDiagnosticsHost, CompilerOptions, IScriptSnapshot, ParsedCommandLine, LanguageService, Diagnostic } from "typescript";
-import type { Context } from "vm";
+/**
+ * Import will remove at compile time
+ */
+export {};
+
+/**
+ * Imports
+ */
+/**
+ * Represents an error specific to the xBuild process.
+ *
+ * The `xBuildError` class extends the `BaseError` class to provide a custom error type for the xBuild system.
+ * It includes additional functionality to maintain stack trace information and assigns a specific name to
+ * the error, making it easier to identify and handle in different parts of the application.
+ *
+ * @augments BaseError
+ */
+declare class xBuildError extends BaseError {
+    /**
+     * Original error stack
+     */
+    originalErrorStack: string | undefined;
+    /**
+     * Creates an instance of `xBuildError`.
+     *
+     * @param message - The error message that describes the error. This message is passed to the base class
+     *   `BaseError` constructor and is used to provide context about the nature of the error.
+     * @param options - Optional configuration for the error. This can include additional properties or settings
+     *   that customize the error's behavior.
+     */
+    constructor(message: string, options?: ErrorOptions);
+}
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * A base class for custom errors with enhanced stack trace formatting and source code information.
+ *
+ * The `BaseError` class extends the native `Error` class, adding functionality to format the error stack
+ * trace and include details from a source map service. This is useful for debugging errors in compiled
+ * or transpiled code by providing clearer information about the source of the error.
+ */
+export declare abstract class BaseError extends Error {
+    readonly sourceMap?: SourceService | undefined;
+    callStacks: Array<NodeJS.CallSite>;
+    /**
+     * Creates a new instance of `BaseError`.
+     *
+     * This constructor initializes a new `BaseError` instance by setting the error message and formatting
+     * the stack trace using the provided source map information. It also ensures the stack trace is maintained
+     * correctly by using `Error.captureStackTrace` (if available). The default source map service is used if
+     * none is provided.
+     *
+     * @param message - A descriptive error message to be associated with the error.
+     * @param sourceMap - (Optional) The `SourceService` instance used to format and resolve the stack trace.
+     *                    If not provided, the default source map service (`defaultSourceService`) is used.
+     */
+    protected constructor(message: string, sourceMap?: SourceService | undefined);
+    /**
+     * Reformats the error stack trace using source map information.
+     *
+     * This function enhances the original error stack trace by attempting to map each entry
+     * back to its original position in the source file using the provided source map service.
+     * If the source map information is not available, it returns the original stack trace.
+     *
+     * @param error - The original error with stack trace of the error.
+     * @returns The reformatted stack trace or the original stack trace if no mapping is available.
+     */
+    protected reformatStack(error: ErrorType): string;
+}
+
+/**
+ * A custom error type that extends the native `Error` object by adding a `callStacks` property.
+ * This property contains an array of `NodeJS.CallSite` objects, representing the call stack details.
+ */
 /**
  * Represents an enhanced error type that extends the built-in Error object.
  * This type adds an optional property to store call stack information.
@@ -25,7 +120,7 @@ import type { Context } from "vm";
  * console.error(myError);
  * ```
  */
-export type ErrorType = Error & {
+type ErrorType = Error & {
     callStacks?: Array<NodeJS.CallSite>;
 };
 /**
@@ -36,7 +131,7 @@ export type ErrorType = Error & {
  * @property blockCode - The block of code (if any) related to the error, or `null` if unavailable.
  * @property formattedError - A formatted string representing the error details.
  */
-export interface StackTraceStateInterface {
+interface StackTraceStateInterface {
     error: ErrorType & BaseError;
     blockCode: null | string;
     formattedError: string;
@@ -50,12 +145,31 @@ export interface StackTraceStateInterface {
  * @property source - The source file path where the frame occurred.
  * @property functionName - The name of the function being executed at this frame, or an empty string if not available.
  */
-export interface FrameDetailsInterface {
+interface FrameDetailsInterface {
     line: number;
     column: number;
     source: string;
     functionName: string;
 }
+
+/**
+ * Import will remove at compile time
+ */
+declare const xBuildLazy: {
+    service: SourceService;
+};
+/**
+ * Prepares the error stack trace for display.
+ *
+ * This function overrides the default stack trace preparation to provide a custom format,
+ * including enhanced stack trace information and error details.
+ *
+ * @param error - The error object (Error or BaseError).
+ * @param stackEntries - The array of stack entries from the call stack.
+ * @returns The formatted stack trace as a string.
+ */
+declare function formatStackTrace(error: ErrorType & BaseError, stackEntries: Array<NodeJS.CallSite>): string;
+
 /**
  * An enumeration of ANSI color codes used for text formatting in the terminal.
  *
@@ -70,7 +184,7 @@ export interface FrameDetailsInterface {
  * console.log(Color.BrightPink, 'This is bright pink text', Color.Reset);
  * ```
  */
-export declare const enum Colors {
+declare const enum Colors {
     Reset = "\u001B[0m",
     Red = "\u001B[38;5;9m",
     Gray = "\u001B[38;5;243m",
@@ -114,80 +228,14 @@ export declare const enum Colors {
  * console.log(plainMessage); // Output will be without color formatting
  * ```
  */
-export declare function setColor(color: Colors, msg: string, activeColor?: boolean): string;
-export declare const xBuildLazy: {
-    service: SourceService;
-};
-/**
- * Prepares the error stack trace for display.
- *
- * This function overrides the default stack trace preparation to provide a custom format,
- * including enhanced stack trace information and error details.
- *
- * @param error - The error object (Error or BaseError).
- * @param stackEntries - The array of stack entries from the call stack.
- * @returns The formatted stack trace as a string.
- */
-export declare function formatStackTrace(error: ErrorType & BaseError, stackEntries: Array<NodeJS.CallSite>): string;
+declare function setColor(color: Colors, msg: string, activeColor?: boolean): string;
+
 /**
- * A base class for custom errors with enhanced stack trace formatting and source code information.
- *
- * The `BaseError` class extends the native `Error` class, adding functionality to format the error stack
- * trace and include details from a source map service. This is useful for debugging errors in compiled
- * or transpiled code by providing clearer information about the source of the error.
+ * Import will remove at compile time
  */
-export declare abstract class BaseError extends Error {
-    readonly sourceMap?: SourceService | undefined;
-    callStacks: Array<NodeJS.CallSite>;
-    /**
-     * Creates a new instance of `BaseError`.
-     *
-     * This constructor initializes a new `BaseError` instance by setting the error message and formatting
-     * the stack trace using the provided source map information. It also ensures the stack trace is maintained
-     * correctly by using `Error.captureStackTrace` (if available). The default source map service is used if
-     * none is provided.
-     *
-     * @param message - A descriptive error message to be associated with the error.
-     * @param sourceMap - (Optional) The `SourceService` instance used to format and resolve the stack trace.
-     *                    If not provided, the default source map service (`defaultSourceService`) is used.
-     */
-    protected constructor(message: string, sourceMap?: SourceService | undefined);
-    /**
-     * Reformats the error stack trace using source map information.
-     *
-     * This function enhances the original error stack trace by attempting to map each entry
-     * back to its original position in the source file using the provided source map service.
-     * If the source map information is not available, it returns the original stack trace.
-     *
-     * @param error - The original error with stack trace of the error.
-     * @returns The reformatted stack trace or the original stack trace if no mapping is available.
-     */
-    protected reformatStack(error: ErrorType): string;
-}
 /**
- * Represents an error specific to the xBuild process.
- *
- * The `xBuildError` class extends the `BaseError` class to provide a custom error type for the xBuild system.
- * It includes additional functionality to maintain stack trace information and assigns a specific name to
- * the error, making it easier to identify and handle in different parts of the application.
- *
- * @augments BaseError
+ * Imports
  */
-export declare class xBuildError extends BaseError {
-    /**
-     * Original error stack
-     */
-    originalErrorStack: string | undefined;
-    /**
-     * Creates an instance of `xBuildError`.
-     *
-     * @param message - The error message that describes the error. This message is passed to the base class
-     *   `BaseError` constructor and is used to provide context about the nature of the error.
-     * @param options - Optional configuration for the error. This can include additional properties or settings
-     *   that customize the error's behavior.
-     */
-    constructor(message: string, options?: ErrorOptions);
-}
 /**
  * A custom error class to handle errors occurring within a virtual machine (VM) execution context.
  *
@@ -208,7 +256,7 @@ export declare class xBuildError extends BaseError {
  * }
  * ```
  */
-export declare class VMRuntimeError extends BaseError {
+declare class VMRuntimeError extends BaseError {
     /**
      * The original error thrown during the VM execution.
      */
@@ -240,58 +288,73 @@ export declare class VMRuntimeError extends BaseError {
      */
     constructor(originalError: ErrorType, sourceMap?: SourceService);
 }
+
 /**
- * Interface for the build state that users can modify.
- *
- * This interface allows users to store and manage any custom data related to the build process.
- *
- * @template T - The type of values that can be stored in the state.
+ * Exports
  */
-export interface PluginsBuildStateInterface {
-    [key: string]: unknown;
-}
 /**
- * A type that defines the possible return values of a plugin function.
- *
- * The function can return a Promise that resolves to `null` or `void`, or it can return `null` or `void` directly.
+ * Import will remove at compile time
  */
-export type PluginResultType = Promise<null | void> | null | void;
 /**
- * Defines the signature of a function that is called at the end of the build process.
- *
- * @param result - The `BuildResult` object that contains information about the outcome of the build process.
- * @param state - The current build state that users can modify.
- * @returns A `PluginResultType`, which may include asynchronous operations.
+ * Imports
  */
-export type OnEndType = (result: BuildResult, state: PluginsBuildStateInterface) => PluginResultType | OnEndResult | Promise<OnEndResult>;
+import '@errors/stack.error';
+import '@errors/uncaught.error';
 /**
- * Defines the signature of a function that is called at the start of the build process.
+ * Main run function that initiates the build process based on CLI arguments.
  *
- * @param build - The `PluginBuild` object that contains information about the build process and allows modifying build options.
- * @param state - The current build state that users can modify.
- * @returns A `PluginResultType`, which may include asynchronous operations.
+ * This function parses the CLI arguments, configures the build settings, and executes
+ * the appropriate build tasks, including type checking, serving, or running in debug mode.
+ *
+ * @param argv - An array of strings representing the CLI arguments.
+ *
+ * @returns A promise that resolves when all build tasks are completed.
+ *
+ * @example
+ * ```ts
+ * await buildWithArgv(process.argv);
+ * ```
  */
-export type OnStartType = (build: PluginBuild, state: PluginsBuildStateInterface) => PluginResultType | OnEndResult | Promise<OnEndResult>;
+declare function buildWithArgv(argv: Array<string>): Promise<void>;
 /**
- * Defines the signature of a function that is called during the resolution of an import path.
+ * Builds the project using a configuration file specified by its path.
  *
- * @param args - The `OnResolveArgs` object, containing information about the file being resolved, such as its path, importer, namespace, etc.
- * @param state - The current build state that users can modify.
- * @returns A `Promise` or a direct `OnResolveResult` which can modify the resolved path, or a `PluginResultType` for
- * performing additional async tasks without altering resolution.
+ * This function reads the configuration from the provided file path, processes it,
+ * and initiates the build tasks.
+ *
+ * @param configFilePath - The path to the configuration file to be used for the build.
+ *
+ * @returns A promise that resolves to an array of `BuildResult` objects once all build tasks are completed.
+ *
+ * @throws Error Throws an error if the configuration file does not exist or is invalid.
+ *
+ * @example
+ * ```ts
+ * const results = await buildWithPath('./config.ts');
+ * console.log('Build results:', results);
+ * ```
  */
-export type OnResolveType = (args: OnResolveArgs, state: PluginsBuildStateInterface) => Promise<OnResolveResult | PluginResultType> | OnResolveResult | PluginResultType;
+declare function buildWithConfigPath(configFilePath: string): Promise<BuildResult[]>;
 /**
- * Defines the signature of a function that is called when a file is loaded.
+ * Builds the project based on the provided configuration object.
  *
- * @param content - The content of the file being loaded, as either a `string` or `Uint8Array`.
- * @param loader - The type of loader used for the file, such as `js`, `ts`, `json`, or others. It can also be `undefined`.
- * @param args - The `OnLoadArgs` object, containing information about the file being loaded, such as its path, namespace, etc.
- * @param state - The current build state that users can modify.
- * @returns A `Promise` or direct `OnLoadResult`, which can modify the file content and loader, or a `PluginResultType`
- * for performing additional async tasks without altering the content.
+ * This function processes the given configuration and executes the build tasks accordingly.
+ *
+ * @param config - A partial configuration object used to define the build settings.
+ *
+ * @returns A promise that resolves to an array of `BuildResult` objects once all build tasks are completed.
+ *
+ * @example
+ * ```ts
+ * const results = await build({ entryPoints: ['./src/index.ts'] });
+ * console.log('Build results:', results);
+ * ```
+ */
+declare function build(config: PartialDeepConfigurationsType): Promise<BuildResult[]>;
+
+/**
+ * Import will remove at compile time
  */
-export type OnLoadType = (content: string | Uint8Array, loader: Loader | undefined, args: OnLoadArgs, state: PluginsBuildStateInterface) => Promise<OnLoadResult | PluginResultType> | OnLoadResult | PluginResultType;
 /**
  * Represents the format for specifying entry points in TypeScript declaration generation and esbuild configuration.
  *
@@ -332,7 +395,7 @@ export type OnLoadType = (content: string | Uint8Array, loader: Loader | undefin
  * When used with esbuild configuration, the format determines how output files are named and structured.
  * When used for TypeScript declaration generation, it affects how declaration files are generated and organized.
  */
-export type EntryPointsType = (string | {
+type EntryPointsType = (string | {
     in: string;
     out: string;
 })[] | Record<string, string> | undefined;
@@ -381,7 +444,7 @@ export type EntryPointsType = (string | {
  * // }
  * ```
  */
-export type PartialDeepType<T> = {
+type PartialDeepType<T> = {
     [P in keyof T]?: T[P] extends object ? PartialDeepType<T[P]> : T[P];
 };
 /**
@@ -401,7 +464,7 @@ export type PartialDeepType<T> = {
  * @property [exports.default] - An optional default export.
  * The default export, if present, is of type `ConfigurationInterface`.
  */
-export interface ModuleInterface {
+interface ModuleInterface {
     /**
      * An object representing the exports of the module.
      * The keys are strings representing export names, and the values can be of any type.
@@ -441,7 +504,7 @@ export interface ModuleInterface {
  *
  * @public
  */
-export interface ServeInterface {
+interface ServeInterface {
     port: number;
     host: string;
     active: boolean;
@@ -495,7 +558,7 @@ export interface ServeInterface {
  * @see OnStartType
  * @see OnResolveType
  */
-export interface HooksInterface {
+interface HooksInterface {
     onEnd: OnEndType;
     onLoad: OnLoadType;
     onStart: OnStartType;
@@ -540,7 +603,7 @@ export interface HooksInterface {
  * @public
  * @category Configuration
  */
-export interface ConfigurationInterface {
+interface ConfigurationInterface {
     /**
      * Build and run entryPoint for development
      */
@@ -674,7 +737,7 @@ interface ExportedConfigurationInterface extends ConfigurationInterface {
  * `ConfigurationInterface` are optional. It allows for flexible configuration
  * objects where only a subset of properties need to be specified.
  */
-export type xBuildConfig = PartialDeepType<ExportedConfigurationInterface>;
+type xBuildConfig = PartialDeepType<ExportedConfigurationInterface>;
 /**
  * Represents a partially deep configuration type based on the `ConfigurationInterface`.
  *
@@ -682,7 +745,7 @@ export type xBuildConfig = PartialDeepType<ExportedConfigurationInterface>;
  * missing or undefined. It leverages the `PartialDeepType` utility type to allow
  * for flexibility in configuration management.
  */
-export type PartialDeepConfigurationsType = PartialDeepType<ConfigurationInterface>;
+type PartialDeepConfigurationsType = PartialDeepType<ConfigurationInterface>;
 /**
  * Defines the possible types for configurations.
  *
@@ -723,1310 +786,1371 @@ export type PartialDeepConfigurationsType = PartialDeepType<ConfigurationInterfa
  * ];
  * ```
  */
-export type ConfigurationsType = PartialDeepConfigurationsType | Array<PartialDeepConfigurationsType>;
+type ConfigurationsType = PartialDeepConfigurationsType | Array<PartialDeepConfigurationsType>;
+export {};
+
 /**
- * Interface representing the command-line arguments for the build tool.
+ * Import will remove at compile time
+ */
+/**
+ * Interface for the build state that users can modify.
  *
- * @interface ArgvInterface
- * @property typeCheck - Flag indicating if the tool should perform type checking only.
- * @property node - Flag indicating if the build is intended for Node.js environment.
- * @property file - The entry file(s) to build.
- * @property dev - List of development-related options for the build.
- * @property debug - List of debugging-related options for the build.
- * @property serve - Flag indicating if an HTTP server should be started for the build folder.
- * @property outdir - The output directory for the build files.
- * @property declaration - Flag indicating if TypeScript declaration files should be generated.
- * @property watch - Flag indicating if the build should watch for file changes.
- * @property config - Path to the build configuration file (JavaScript or TypeScript).
- * @property tsconfig - Path to the TypeScript configuration file to use.
- * @property minify - Flag indicating if the code should be minified.
- * @property bundle - Flag indicating if the code should be bundled.
- * @property format - Defines the formats for the build output.
+ * This interface allows users to store and manage any custom data related to the build process.
+ *
+ * @template T - The type of values that can be stored in the state.
  */
-export interface ArgvInterface {
-    typeCheck: boolean;
-    node: boolean;
-    file: string;
-    dev: Array<string>;
-    debug: Array<string>;
-    serve: boolean;
-    outdir: string;
-    declaration: boolean;
-    watch: boolean;
-    config: string;
-    tsconfig: string;
-    minify: boolean;
-    bundle: boolean;
-    format: Format;
+interface PluginsBuildStateInterface {
+    [key: string]: unknown;
 }
 /**
- * Parses command-line arguments into an `ArgvInterface` object using `yargs`.
- *
- * This function configures `yargs` to handle various build-related options for a JavaScript and TypeScript toolchain.
- * It returns an object that adheres to the `ArgvInterface` structure based on the parsed arguments.
- *
- * @param argv - An array of command-line arguments (e.g., `process.argv`).
- * @returns An object representing the parsed command-line arguments.
+ * A type that defines the possible return values of a plugin function.
  *
- * @see {@link ArgvInterface} for the structure of the returned object.
+ * The function can return a Promise that resolves to `null` or `void`, or it can return `null` or `void` directly.
+ */
+type PluginResultType = Promise<null | void> | null | void;
+/**
+ * Defines the signature of a function that is called at the end of the build process.
  *
- * @example
- * // Example usage:
- * const args = argvParser(process.argv);
- * console.log(args.file); // Output: the file to build
- * console.log(args.dev); // Output: true or false based on the --dev flag
+ * @param result - The `BuildResult` object that contains information about the outcome of the build process.
+ * @param state - The current build state that users can modify.
+ * @returns A `PluginResultType`, which may include asynchronous operations.
  */
-export declare function argvParser(argv: Array<string>): Argv<ArgvInterface>;
+type OnEndType = (result: BuildResult, state: PluginsBuildStateInterface) => PluginResultType | OnEndResult | Promise<OnEndResult>;
 /**
- * The `BuildStateInterface` extends the `PluginsBuildStateInterface` interface to include additional properties related to the build
- * process, specifically for handling `ifdef` conditions and function removals in macros.
+ * Defines the signature of a function that is called at the start of the build process.
  *
- * @interface BuildStateInterface
+ * @param build - The `PluginBuild` object that contains information about the build process and allows modifying build options.
+ * @param state - The current build state that users can modify.
+ * @returns A `PluginResultType`, which may include asynchronous operations.
  */
-export interface BuildStateInterface extends PluginsBuildStateInterface {
-    ifdef: Array<string>;
-    macros: {
-        removeFunctions: Set<string>;
-    };
-}
+type OnStartType = (build: PluginBuild, state: PluginsBuildStateInterface) => PluginResultType | OnEndResult | Promise<OnEndResult>;
 /**
- * Custom error class to represent type-related errors.
+ * Defines the signature of a function that is called during the resolution of an import path.
  *
- * This class extends the built-in `Error` class to provide more specific
- * error handling for issues related to types. It can be used to distinguish
- * errors that occur due to type mismatches or other type-related problems
- * in your application.
+ * @param args - The `OnResolveArgs` object, containing information about the file being resolved, such as its path, importer, namespace, etc.
+ * @param state - The current build state that users can modify.
+ * @returns A `Promise` or a direct `OnResolveResult` which can modify the resolved path, or a `PluginResultType` for
+ * performing additional async tasks without altering resolution.
+ */
+type OnResolveType = (args: OnResolveArgs, state: PluginsBuildStateInterface) => Promise<OnResolveResult | PluginResultType> | OnResolveResult | PluginResultType;
+/**
+ * Defines the signature of a function that is called when a file is loaded.
  *
- * @example
- * ```ts
- * throw new TypesError('Invalid type encountered.');
- * ```
+ * @param content - The content of the file being loaded, as either a `string` or `Uint8Array`.
+ * @param loader - The type of loader used for the file, such as `js`, `ts`, `json`, or others. It can also be `undefined`.
+ * @param args - The `OnLoadArgs` object, containing information about the file being loaded, such as its path, namespace, etc.
+ * @param state - The current build state that users can modify.
+ * @returns A `Promise` or direct `OnLoadResult`, which can modify the file content and loader, or a `PluginResultType`
+ * for performing additional async tasks without altering the content.
+ */
+type OnLoadType = (content: string | Uint8Array, loader: Loader | undefined, args: OnLoadArgs, state: PluginsBuildStateInterface) => Promise<OnLoadResult | PluginResultType> | OnLoadResult | PluginResultType;
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * Interface representing the command-line arguments for the build tool.
  *
- * @augments Error
+ * @interface ArgvInterface
+ * @property typeCheck - Flag indicating if the tool should perform type checking only.
+ * @property node - Flag indicating if the build is intended for Node.js environment.
+ * @property file - The entry file(s) to build.
+ * @property dev - List of development-related options for the build.
+ * @property debug - List of debugging-related options for the build.
+ * @property serve - Flag indicating if an HTTP server should be started for the build folder.
+ * @property outdir - The output directory for the build files.
+ * @property declaration - Flag indicating if TypeScript declaration files should be generated.
+ * @property watch - Flag indicating if the build should watch for file changes.
+ * @property config - Path to the build configuration file (JavaScript or TypeScript).
+ * @property tsconfig - Path to the TypeScript configuration file to use.
+ * @property minify - Flag indicating if the code should be minified.
+ * @property bundle - Flag indicating if the code should be bundled.
+ * @property format - Defines the formats for the build output.
  */
-export declare class TypesError extends Error {
-    /**
-     * Creates an instance of `TypesError`.
-     *
-     * @param message - A human-readable message providing details about the error.
-     * @param options - Optional configuration for the error, such as a `cause` (ECMAScript 2022+).
-     */
-    constructor(message?: string, options?: {
-        cause?: Error;
-    });
+interface ArgvInterface {
+    typeCheck: boolean;
+    node: boolean;
+    file: string;
+    dev: Array<string>;
+    debug: Array<string>;
+    serve: boolean;
+    outdir: string;
+    declaration: boolean;
+    watch: boolean;
+    config: string;
+    tsconfig: string;
+    minify: boolean;
+    bundle: boolean;
+    format: Format;
 }
+
 /**
- * Spawns a new Node.js process to execute the provided JavaScript file, with optional debugging support.
- *
- * This function creates a new Node.js process to run the specified JavaScript file with source map support enabled.
- * It optionally starts the process in debug mode, which allows WebStorm or other debuggers to attach to the process.
- * The output and error streams of the spawned process are captured and logged to the console.
- *
- * @param filePath - The path to the JavaScript file to execute.
- * @param debug - A boolean flag to enable debugging. If `true`, the process will be started with the `--inspect-brk` option,
- * which opens a debugger on `0.0.0.0:9229`, allowing external debuggers to attach.
- *
- * @returns A `ChildProcessWithoutNullStreams` object representing the spawned process.
- * This object allows interaction with the process, including capturing its output and error streams.
+ * Handles uncaught exceptions in the Node.js process.
  *
- * @remarks
- * - The `--enable-source-maps` flag is used to enable source map support, which allows better debugging by mapping
- *   errors and stack traces to the original source code.
- * - If `debug` is `true`, the `--inspect-brk=0.0.0.0:9229` flag is added, starting the process in debug mode and pausing
- *   execution until a debugger is attached.
- * - The output (`stdout`) and error (`stderr`) streams of the spawned process are logged to the console.
- * - The function returns a `ChildProcessWithoutNullStreams` object that can be used to interact with the spawned process,
- *   such as handling its termination or sending input.
+ * This handler is triggered when an error is thrown that is not caught by any try-catch blocks.
+ * It captures such exceptions and logs them to the console. If the exception is an instance of `Error`,
+ * its string representation is logged. Otherwise, the raw error object is logged.
  *
- * @throws Error Throws an error if the Node.js process fails to start or if there are issues with the provided file path.
+ * This setup helps in debugging by ensuring that all uncaught exceptions are logged, providing visibility
+ * into errors that might otherwise go unnoticed.
  *
  * @example
  * ```ts
- * import { spawn } from '@services/process.service';
- *
- * // Run without debugging
- * const process = spawn('./path/to/script.js', false);
- *
- * process.on('close', (code) => {
- *     console.log(`Process exited with code ${code}`);
- * });
- *
- * // Run with debugging enabled
- * const debugProcess = spawn('./path/to/script.js', true);
- *
- * debugProcess.on('close', (code) => {
- *     console.log(`Debug process exited with code ${code}`);
+ * process.on('uncaughtException', (error) => {
+ *     if (error instanceof Error) {
+ *         console.error(error.toString());
+ *     } else {
+ *         console.error(error);
+ *     }
  * });
  * ```
  *
- * In these examples, the `spawn` function is used to execute a JavaScript file, once in normal mode and once with debugging enabled.
- * The process's exit code is logged when the process completes.
- *
- * @public
- * @category Services
+ * @throws Will log uncaught exceptions to the console.
+ * Custom handling logic should be added if additional error handling or logging is required.
+ */
+export {};
+
+/**
+ * Import will remove at compile time
  */
-export declare function spawn(filePath: string, debug?: boolean): ChildProcessWithoutNullStreams;
 /**
- * Represents the result of transpiling a TypeScript file.
+ * Parses command-line arguments into an `ArgvInterface` object using `yargs`.
  *
- * This interface defines the structure of the output returned from a TypeScript transpilation process,
- * including the transpiled JavaScript code and the associated source map.
+ * This function configures `yargs` to handle various build-related options for a JavaScript and TypeScript toolchain.
+ * It returns an object that adheres to the `ArgvInterface` structure based on the parsed arguments.
  *
- * @property code - The transpiled JavaScript code generated from the TypeScript file.
- * @property sourceMap - The source map associated with the transpiled JavaScript code.
+ * @param argv - An array of command-line arguments (e.g., `process.argv`).
+ * @returns An object representing the parsed command-line arguments.
  *
- * @remarks
- * - The `code` property contains the JavaScript code after TypeScript transpilation.
- * - The `sourceMap` property provides the source map that maps the transpiled JavaScript code back to the original TypeScript source.
- * - The source map is useful for debugging as it allows developers to trace errors in the generated JavaScript back to the original TypeScript code.
+ * @see {@link ArgvInterface} for the structure of the returned object.
  *
  * @example
- * ```typescript
- * import { TranspileFileInterface } from './TranspileFileInterface';
- *
- * const result: TranspileFileInterface = {
- *     code: 'console.log("Hello, world!");',
- *     sourceMap: 'version: 3\nfile: out.js\nsources: ["file.ts"]\n'
- * };
- *
- * console.log(result.code); // Output: console.log("Hello, world!");
- * console.log(result.sourceMap); // Output: version: 3\nfile: out.js\nsources: ["file.ts"]\n
- * ```
- *
- * In this example, the `TranspileFileInterface` is used to represent the result of transpiling a TypeScript file.
- * The `code` contains the JavaScript code, while the `sourceMap` provides the mapping information for debugging purposes.
- *
- * @public
- * @category Interfaces
- */
-export interface TranspileFileInterface {
-    code: string;
-    sourceMap: string;
-}
-/**
- * Default build options for esbuild bundler in RemoteX framework.
- *
- * These options are used to configure how esbuild processes and bundles the TypeScript
- * files for the RemoteX testing framework.
- *
- * @public
- * @category Configuration
+ * // Example usage:
+ * const args = argvParser(process.argv);
+ * console.log(args.file); // Output: the file to build
+ * console.log(args.dev); // Output: true or false based on the --dev flag
  */
-export declare const defaultBuildOptions: BuildOptions;
+declare function argvParser(argv: Array<string>): Argv<ArgvInterface>;
+
 /**
- * Extracts the source map from the provided data string and returns the modified code and source map separately.
- *
- * This function searches for the inline source map in the data string using a regular expression, removes the
- * source map comment from the data string, and returns an object containing the code without the source map
- * comment and the extracted source map.
- *
- * @param dataString - The string containing the transpiled code with an inline source map.
- * @returns An object containing the modified code without the source map comment and the extracted source map.
- * @throws Error -Throws an error if the source map URL is not found in the data string.
- *
- * @public
+ * Import will remove at compile time
  */
-export declare function extractSourceMap(dataString: string): TranspileFileInterface;
 /**
- * Transpiles a TypeScript file and extracts the source map.
+ * Manages the build process for a TypeScript project using esbuild.
  *
- * This function uses esbuild to transpile the specified TypeScript file based on provided build options,
- * and then extracts the source map from the transpiled code.
+ * The `BuildService` class orchestrates the build process, including TypeScript compilation, handling of build errors,
+ * and lifecycle management of the build. It can operate in various modes, such as watching for file changes or running
+ * in development mode. It also provides functionality for spawning development processes and processing entry points.
  *
- * @param filePath - The path to the TypeScript file to be transpiled.
- * @param buildOptions - Optional build options to override the default build options.
- * @returns A promise that resolves to an object containing the transpiled code and the extracted source map.
- * @throws Error - Throws an error if the build process fails or the source map extraction fails.
+ * @remarks
+ * - The build process can be configured using the provided `ConfigurationInterface`.
+ * - Errors related to TypeScript are handled separately and are not logged by default.
+ * - The class supports various build modes, including watch mode and development mode, and handles different scenarios
+ *   based on the configuration.
  *
  * @public
  * @category Services
  */
-export declare function transpileFile(filePath: string, buildOptions?: BuildOptions): Promise<TranspileFileInterface>;
-/**
- * The `analyzeDependencies` function analyzes the dependencies of a given entry point for a specified platform.
- * It performs a bundling operation and generates a metafile that contains detailed information about the
- * dependencies involved in the build process.
- * This is typically used to inspect the external packages and modules
- * that the entry point depends on.
- *
- * - **Input**:
- *   - `entryPoint`: A string or array of strings representing the entry points for the build.
- *   This defines the starting point(s) for the bundling process.
- *   - `platform`: An optional parameter that specifies the platform to target for the build.
- *   Default is `'browser'`.
- *
- * - **Output**: A `Promise` that resolves to an object containing:
- *   - The `BuildResult` from the bundling process.
- *   - A `metafile`, which contains detailed metadata about the build, including the dependencies analyzed.
- *
- * ## Example:
- *
- * ```ts
- * const result = await analyzeDependencies(['src/index.ts']);
- * console.log(result.metafile); // { inputs: { 'src/index.ts': { ... } }, outputs: { ... } }
- *
- * const nodeResult = await analyzeDependencies(['src/server.ts'], 'node');
- * console.log(nodeResult.metafile); // { inputs: { 'src/server.ts': { ... } }, outputs: { ... } }
- * ```
- *
- * @param entryPoint - The entry point(s) to be analyzed.
- * @param platform - The target platform for the build.
- * @returns A `Promise` that resolves to a `BuildResult` object along with a `metafile` containing dependency details.
- * @throws Error If the build process fails for any reason.
- */
-export declare function analyzeDependencies(entryPoint: EntryPointsType, platform?: BuildOptions['platform']): Promise<BuildResult & {
-    metafile: Metafile;
-}>;
-/**
- * The `collectFunctionNames` function analyzes the provided TypeScript code and collects the names of functions
- * that should be removed based on specific conditions. The function searches for function declarations and variable
- * declarations where the function name or variable is prefixed with `$$`, and adds these function names to the
- * `removeFunctions` set in the provided `state` object.
- *
- * - **Input**:
- *   - `code`: A string containing the TypeScript code to be analyzed.
- *   - `state`: An object representing the current build state, specifically the `mocks` state, which includes
- *     a `removeFunctions` set that will hold the names of functions that need to be removed.
- *
- * - **Output**: The function does not return any value. Instead, it modifies the `removeFunctions` set inside the
- *   `state` object by adding function names that meet the criteria for removal.
- *
- * ## Error Handling:
- * - The function does not explicitly handle errors. If invalid TypeScript code is provided, `ts.createSourceFile`
- *   may throw an error, which should be handled by the caller if necessary.
- *
- * @param code - The TypeScript code as a string that will be analyzed.
- * @param state - The build state containing the `removeFunctions` set to store the names of functions to be removed.
- * @returns `void` - The function modifies the `state` directly and does not return a value.
- */
-export declare function collectFunctionNames(code: string, state: BuildStateInterface['macros']): void;
-/**
- * The `collectDeclaredFunctions` function processes the provided `meta` metafile and reads each file's contents
- * to find function declarations within preprocessor directives. It uses regular expressions to match `// ifdef` and
- * `// endif` blocks in the code and collects the function names from the code inside the `ifdef` block, based on the
- * `define` configuration in the `config` object. If the condition defined in the `ifdef` is not met (i.e., not defined
- * in the `config.define`), the function names found inside the block will be collected and added to the `removeFunctions`
- * set in the `state` object.
- *
- * - **Input**:
- *   - `meta`: The `Metafile` object that contains the input files. The keys are file paths, and the values contain
- *     metadata about those files.
- *   - `config`: The configuration object containing a `define` field, which is an object of conditions that may be used
- *     in the `ifdef` blocks. If a condition in an `ifdef` block is not defined in `config.define`, the functions in
- *     that block will be collected.
- *   - `state`: The build state, specifically the `mocks` state, which includes a `removeFunctions` set that stores
- *     function names to be removed.
- *
- * - **Output**: This function does not return a value. It modifies the `removeFunctions` set within the provided `state`
- *   object by adding the names of functions found inside unprocessed `ifdef` blocks.
- *
- * ## Error Handling:
- * - If a file cannot be read due to a filesystem error, the function will throw an error.
- * - If the provided `meta` or `config` is malformed, it may result in runtime errors. The caller should ensure valid input.
- *
- * @param meta - The `Metafile` object containing the list of input files and their metadata.
- * @param config - The configuration object that defines conditions used in `ifdef` blocks.
- * @param state - The build state containing the `removeFunctions` set to store function names to be removed.
- * @returns `void` - The function modifies the `state` directly and does not return a value.
- */
-export declare function collectDeclaredFunctions(meta: Metafile, config: ConfigurationInterface, state: BuildStateInterface['macros']): Promise<void>;
-/**
- * The `parseMacros` function processes TypeScript or JavaScript files to transform macros defined within the content.
- * It ensures that the build state is initialized if necessary, analyzes file dependencies, collects declared functions
- * that are marked for removal, and applies transformations to the source code based on the macros.
- * If the file's extension is not `.ts` or `.js`, the function returns `undefined`. Otherwise, it transforms the code
- * and returns the result in the specified loader format.
- *
- * - **Input**:
- *   - `content`: The content of the file as a string or `Uint8Array` to be parsed.
- *   - `loader`: A string representing the loader type for transforming the code (e.g., `'ts'`, `'js'`).
- *   - `args`: The `OnLoadArgs` object containing metadata for the current loading process, including the file path.
- *   - `state`: The build state containing the `mocks` object, which includes a `removeFunctions` set that tracks
- *     functions to be removed.
- *   - `config`: The configuration object that defines how macros should be handled (e.g., conditions for macro processing).
- *
- * - **Output**: A `Promise` that resolves to an `OnLoadResult`, `PluginResultType`, or `undefined`. If the file is
- *   of type `.ts` or `.js`, the transformed code is returned in the specified loader format (e.g., `'ts'`). If the file
- *   extension is not recognized, the function returns `undefined`.
- *
- * ## Error Handling:
- * - If the file path does not end with `.ts` or `.js`, the function returns `undefined`.
- * - If `state.mocks` is not initialized, it will be set up by analyzing the file dependencies and collecting declared functions.
- * - If any errors occur during the analysis, function collection, or transformation, the function may throw an error.
- *
- * @param content - The content of the file as a string or `Uint8Array` to be parsed.
- * @param loader - The loader type for transforming the code (e.g., `'ts'` or `'js'`).
- * @param args - The `OnLoadArgs` containing metadata, including the file path.
- * @param state - The build state that includes `mocks` with the `removeFunctions` set.
- * @param config - The configuration object defining how macros should be handled.
- * @returns A `Promise` that resolves to the transformed code (`OnLoadResult` or `PluginResultType`), or `undefined`
- *          if the file is not of type `.ts` or `.js`.
- */
-export declare function parseMacros(content: string | Uint8Array, loader: Loader | undefined, args: OnLoadArgs, state: BuildStateInterface, config: ConfigurationInterface): Promise<OnLoadResult | PluginResultType | undefined>;
-/**
- * Represents an error that occurs during the esbuild process.
- *
- * This class extends the base error class to provide specific error handling for esbuild-related issues.
- * It captures the error message and maintains the proper stack trace, allowing for easier debugging
- * and identification of errors that occur during the build process.
- *
- * @class esBuildError
- * @extends BaseError
- */
-export declare class esBuildError extends BaseError {
-    originalErrorStack?: string;
+declare class BuildService {
+    private config;
     /**
-     * Creates an instance of the EsbuildError class.
-     *
-     * @param message - An object containing the error message. The `text` property is used to initialize
-     * the base error class with a descriptive message about the error encountered during the esbuild process.
+     * Provides TypeScript-related functionality for the build process.
      */
-    constructor(message: Message);
+    readonly typescriptModule: TypescriptModule;
     /**
-     * Generates a formatted error message with highlighted code.
+     * Keeps track of active development processes spawned during the build.
+     * This property holds an array of `ChildProcessWithoutNullStreams` instances that represent Node.js processes spawned
+     * for running development tasks. These processes are used to handle development builds or runtime tasks and are managed
+     * by the `BuildService` class to ensure they are properly started and stopped.
      *
-     * @param message - An esbuild Message object containing error information.
-     * @returns A formatted string of the error message.
-     */
-    private generateFormattedError;
-    /**
-     * Reads code from a file if it exists.
+     * @remarks
+     * - The array is populated when development processes are spawned, such as when specific development files are
+     *   processed or when running in development mode.
+     * - The processes are terminated gracefully at the end of the build to avoid leaving orphaned processes running.
+     * - It is important to manage these processes correctly to avoid resource leaks and ensure proper cleanup.
      *
-     * @param path - The file path to read from.
-     * @returns Array of lines if file exists, otherwise null.
+     * @see ChildProcessWithoutNullStreams
      */
-    private readCode;
+    private activePossess;
     /**
-     * Formats a code snippet with highlighted errors.
+     * Plugin provider
      *
-     * @param code - Array of code lines.
-     * @param location - The error location within the file.
-     * @returns A formatted and highlighted code snippet string.
+     * @private
      */
-    private formatCodeSnippet;
+    private pluginsProvider;
     /**
-     * Applies color to a given text if colors are enabled.
+     * A mapping of output filenames to their corresponding source file paths.
      *
-     * @param color - The color code.
-     * @param text - The text to colorize.
-     * @returns The colorized text if colors are active, otherwise plain text.
-     */
-    private applyColor;
-}
-/**
- * ASCII Logo and Version Information
- *
- * @remarks
- * The `asciiLogo` constant stores an ASCII representation of the project logo
- * that will be displayed in the banner. This banner is rendered in a formatted
- * string in the `bannerComponent` function.
- *
- * The `cleanScreen` constant contains an ANSI escape code to clear the terminal screen.
- */
-export declare const asciiLogo = "\n     ______       _ _     _\n     | ___ \\     (_) |   | |\n__  _| |_/ /_   _ _| | __| |\n\\ \\/ / ___ \\ | | | | |/ _` |\n >  <| |_/ / |_| | | | (_| |\n/_/\\_\\____/ \\__,_|_|_|\\__,_|\n";
-export declare const cleanScreen = "\u001Bc";
-/**
- * Renders the banner with the ASCII logo and version information.
- *
- * This function constructs and returns a formatted banner string that includes an ASCII logo and the version number.
- * The colors used for the ASCII logo and version number can be enabled or disabled based on the `activeColor` parameter.
- * If color formatting is enabled, the ASCII logo will be rendered in burnt orange, and the version number will be in bright pink.
- *
- * @param activeColor - A boolean flag indicating whether ANSI color formatting should be applied. Default is `__ACTIVE_COLOR`.
- *
- * @returns A formatted string containing the ASCII logo, version number, and ANSI color codes if `activeColor` is `true`.
- *
- * @remarks
- * The `bannerComponent` function clears the terminal screen, applies color formatting if enabled, and displays
- * the ASCII logo and version number. The version number is retrieved from the global `__VERSION` variable, and
- * the colors are reset after the text is rendered.
- *
- * @example
- * ```ts
- * console.log(bannerComponent());
- * ```
- *
- * This will output the banner to the console with the ASCII logo, version, and colors.
- *
- * @example
- * ```ts
- * console.log(bannerComponent(false));
- * ```
- *
- * This will output the banner to the console with the ASCII logo and version number without color formatting.
- *
- * @public
- */
-export declare function bannerComponent(activeColor?: boolean): string;
-/**
- * A formatted string prefix used for logging build-related messages.
- * // todo optimize this
- */
-export declare function prefix(): string;
-/**
- * Manages the HTTP or HTTPS server based on the provided configuration.
- *
- * The `ServerProvider` class initializes and starts either an HTTP or HTTPS server based on whether SSL certificates
- * are provided. It handles incoming requests, serves static files, and lists directory contents with appropriate
- * icons and colors.
- *
- * @class
- */
-export declare class ServerProvider {
-    /**
-     * Root dir to serve
-     */
-    private readonly rootDir;
-    /**
-     * Indicates whether the server is configured to use HTTPS.
-     */
-    private readonly isHttps;
-    /**
-     * The server configuration object, including SSL certificate paths and other settings.
-     */
-    private readonly config;
-    /**
-     * Creates an instance of ServerProvider.
+     * @remarks
+     * This property stores the entry points configuration for TypeScript compilation.
+     * - Keys represent the output filenames (with or without .d.ts extension)
+     * - Values represent the source file paths to use as entry points
      *
-     * @param config - The server configuration object, including port number, SSL certificate paths, and an optional request handler.
-     * @param dir - The root directory from which to serve files.
+     * Used by declaration bundling operations to determine which files to process
+     * and how to name the resulting declaration outputs.
      *
      * @example
      * ```ts
-     * import { ServerProvider } from './server-provider';
-     *
-     * const serverConfig = {
-     *     port: 8080,
-     *     keyfile: './path/to/keyfile',
-     *     certfile: './path/to/certfile',
-     *     onRequest: (req, res, next) => { /* custom request handling *\/ }
-     * };
-     * const provider = new ServerProvider(serverConfig, './public');
-     * provider.start();
+     * // Example entryPoints structure
+     * {
+     *   'index': 'src/index.ts',
+     *   'components/button': 'src/components/button.ts'
+     * }
      * ```
      *
-     * This example shows how to create an instance of `ServerProvider` and start the server.
+     * @private
+     * @since 1.5.9
      */
-    constructor(config: ServeInterface, dir: string);
+    private readonly entryPoints;
     /**
-     * Starts the server based on the configuration.
-     * If SSL certificates are provided and valid, an HTTPS server is started. Otherwise, an HTTP server is started.
-     *
-     * @example
-     * ```ts
-     * provider.start();
-     * ```
+     * Initializes the build service with the provided configuration.
      *
-     * This example demonstrates how to start the server. It will either start an HTTP or HTTPS server based on the configuration.
-     */
-    start(): void;
-    /**
-     * Starts an HTTP server.
-     * This method creates an HTTP server that listens on the configured port and handles incoming requests.
+     * The constructor configures the TypeScript provider, suppresses esbuild logging,
+     * sets up development modes, and registers the necessary plugins.
      *
-     * @example
-     * ```ts
-     * provider.startHttpServer();
-     * ```
+     * Declaration files will be output based on the following order of precedence:
+     * 1. If `declarationOutDir` is set in the configuration, it will be used.
+     * 2. If `declarationOutDir` is not provided, it will use the `outDir` value from the tsconfig.
+     * 3. If neither of the above is available, it falls back to using the `outdir` specified in the esbuild configuration.
      *
-     * This example shows how the `startHttpServer` method is used internally to start an HTTP server.
+     * @param config - The configuration object for the build process, including esbuild and TypeScript settings.
      */
-    private startHttpServer;
+    constructor(config: ConfigurationInterface);
     /**
-     * Starts an HTTPS server.
+     * Executes the build process.
+     * This method performs the build and handles any errors that occur during the execution.
+     * If watching or development mode is enabled in the configuration, it starts watching for changes
+     * to automatically rebuild as needed.
+     * The method logs errors that are not related to TypeScript
+     * compilation issues.
      *
-     * This method creates an HTTPS server with SSL/TLS certificates, listens on the configured port, and handles incoming requests.
+     * @returns A promise that resolves with a `BuildResult` when the build process is complete,
+     *          or `undefined` if an error occurs during execution.
+     *
+     * @throws Error Throws an error if the build process encounters issues that are not related
+     *                 to TypeScript. Such errors are logged, but the method does not rethrow them.
      *
      * @example
      * ```ts
-     * provider.startHttpsServer();
+     * import { BuildService } from './build-service';
+     *
+     * const buildService = new BuildService(config);
+     * buildService.run().then(() => {
+     *     console.log('Build process completed successfully.');
+     * }).catch((error) => {
+     *     console.error('Build process failed:', error);
+     * });
      * ```
      *
-     * This example shows how the `startHttpsServer` method is used internally to start an HTTPS server.
+     * In this example, the `run` method is invoked to execute the build process. It handles both successful
+     * completion and logs any encountered errors, allowing the user to understand the outcome of the build.
      */
-    private startHttpsServer;
+    run(): Promise<BuildResult | void>;
     /**
-     * Handles incoming requests.
+     * Runs the build process in debug mode for the specified entry points.
+     * This method temporarily disables development and watch mode, initiates the build process, and spawns development processes
+     * for the specified entry points. If any errors occur during the build, they are handled appropriately.
      *
-     * This method checks if a custom request handler is provided in the configuration. If so, it uses the custom handler.
-     * Otherwise, it delegates to the default request handler.
+     * @param entryPoints - An array of entry point file names for which the development processes will be spawned.
+     * These entry points are matched against the build output files.
      *
-     * @param req - The incoming request object.
-     * @param res - The response object.
-     * @param defaultHandler - The default handler functions to be called if no custom handler is provided.
+     * @returns A `Promise<void>` that resolves when the build and process spawning have completed.
+     *
+     * @throws Handles any build-related errors using the `handleErrors` method.
+     *
+     * @remarks
+     * - The `config.dev` and `config.watch` settings are temporarily disabled to prevent development mode or file watching during the build.
+     * - The `build()` method is called to generate the necessary build outputs.
+     * - The `spawnDev` method is then invoked to spawn processes for the matching entry points.
+     * - If any errors occur during the build, they are caught and passed to the `handleErrors` method.
      *
      * @example
      * ```ts
-     * // This method is used internally to handle requests
+     * const entryPoints = ['index', 'main'];
+     * await this.runDebug(entryPoints);
      * ```
+     *
+     * In this example, the `runDebug` method runs the build process and spawns development processes for `index` and `main`.
+     *
+     * @public
      */
-    private handleRequest;
+    runDebug(entryPoints: Array<string>): Promise<void>;
     /**
-     * Returns the MIME type for a given file extension.
+     * Serves the project and watches for changes.
+     * This method starts the development server using the `ServerProvider`, builds the project using esbuild,
+     * and watches for file changes to automatically rebuild as needed. It initializes the server and invokes
+     * the build process, enabling continuous development mode.
      *
-     * This method maps file extensions to their corresponding MIME types.
+     * @returns A promise that resolves when the server is started and the build process is complete.
      *
-     * @param ext - The file extension.
-     * @returns The MIME type associated with the file extension.
+     * @throws This method catches any errors thrown during the build process and handles them using the
+     * `handleErrors` method.
      *
      * @example
      * ```ts
-     * const mimeType = provider.getContentType('html');
-     * console.log(mimeType); // 'text/html'
+     * const buildService = new BuildService(config);
+     * buildService.serve().then(() => {
+     *     console.log('Server is running and watching for changes.');
+     * }).catch((error) => {
+     *     console.error('Failed to start the server:', error);
+     * });
      * ```
+     *
+     * In this example, the `serve` method starts the server and watches for changes. If an error occurs during
+     * the build or server startup, it is handled and logged.
      */
-    private getContentType;
+    serve(): Promise<void>;
     /**
-     * Handles the default response for requests, serving files or directories.
+     * Executes a provided asynchronous callback function within a try-catch block.
+     * This method ensures that any errors thrown during the execution of the callback
+     * are properly handled and logged. If the error appears to be an `esbuild`-related
+     * `OnEndResult` error with an array of errors, it avoids redundant logging.
+     * Otherwise, it wraps the error in a `VMRuntimeError` and logs the stack trace.
      *
-     * This method serves the content of files or directories. If the request is for a directory, it lists the contents with
-     * appropriate icons and colors.
+     * @template T - The return type of the callback function, allowing flexibility
+     *               in the expected result type. Defaults to `BuildResult`.
      *
-     * @param req - The incoming request object.
-     * @param res - The response object.
+     * @param callback - A function that returns a `Promise<T>`, which is executed asynchronously.
+     *                   The callback is wrapped in error handling logic to catch and process any exceptions.
      *
-     * @returns A promise that resolves when the response is sent.
+     * @returns A `Promise<T | void>` that resolves with the result of the callback function if successful,
+     *          or `void` if an error was thrown and handled. This allows for optional chaining on the return value.
      *
-     * @throws  Throws an error if the file or directory cannot be accessed.
+     * @throws This method does not throw explicitly but will log an error message if an exception is caught
+     *         and is not an `esbuild`-related error. The error stack is logged via `VMRuntimeError` for non-esbuild errors.
      *
      * @example
      * ```ts
-     * // This method is used internally to handle file and directory responses
+     * await execute(async () => {
+     *   // Perform some asynchronous operation here
+     *   return someResult;
+     * });
      * ```
      */
-    private defaultResponse;
+    private execute;
     /**
-     * promisifyStat the `fs.stat` method.
+     * Configures the development mode by ensuring that `config.dev` is set properly.
+     */
+    private configureDevelopmentMode;
+    /**
+     * Sets up the plugin's provider and registers the plugin HooksInterface.
+     */
+    private setupPlugins;
+    /**
+     * Registers the plugin HooksInterface for start, end, and load events.
      *
-     * Converts the `fs.stat` callback-based method to return a promise.
+     * @param paths - The resolved path aliases.
+     * @param rootDir - The root directory for resolving paths.
+     */
+    private registerPluginHooks;
+    /**
+     * Generates a path alias object from the TypeScript provider's path options.
+     * This method processes the `paths` property from the TypeScript provider's options,
+     * which is expected to be an object where each key represents a path alias pattern,
+     * and the corresponding value is an array of paths. The method removes any wildcard
+     * characters (`*`) from both the keys and the first values of the arrays. It also
+     * resolves the paths relative to the specified `rootDir`, returning a simplified
+     * object that maps the cleaned keys to their respective paths.
      *
-     * @param path - The file or directory path.
-     * @returns A promise that resolves with the file statistics.
+     * The resolved paths will be formatted to use a relative path notation.
      *
-     * @example
+     * Example:
+     * Given the following paths:
      * ```ts
-     * const stats = await provider.promisifyStat('./path/to/file');
-     * console.log(stats.isFile()); // true or false
+     * {
+     *   '@core/*': ['src/core/*'],
+     *   '@utils/*': ['src/utils/*']
+     * }
+     * ```
+     * And assuming `rootDir` is set to the base directory of your project, the method
+     * will return:
+     * ```ts
+     * {
+     *   '@core/': './core/',
+     *   '@utils/': './utils/'
+     * }
      * ```
+     *
+     * @param rootDir - The root directory to resolve paths against.
+     * @returns An object mapping cleaned path aliases to their respective resolved paths.
      */
-    private promisifyStat;
+    private generatePathAlias;
     /**
-     * Handles directory listings.
+     * Handles errors during the build process.
+     * This method processes and logs errors that occur during the esbuild process. It specifically filters out
+     * errors related to TypeScript (`TypesError`) to prevent them from being logged, while logging all other errors
+     * to the console. The error object is assumed to contain a list of messages, each with detailed information.
      *
-     * Reads the contents of a directory and generates an HTML response with file icons and colors.
+     * @param esbuildError - The error object returned by esbuild, which is expected to contain an array of
+     * error messages.
      *
-     * @param fullPath - The full path to the directory.
-     * @param requestPath - The request path for generating relative links.
-     * @param res - The response object.
+     * @private
+     *
+     * @remarks
+     * - TypeScript errors (denoted as `TypesError`) are skipped and not logged.
+     * - Other errors are logged to the console with their text descriptions.
      *
      * @example
      * ```ts
-     * // This method is used internally to handle directory listings
+     * try {
+     *     await buildService.run();
+     * } catch (esbuildError) {
+     *     buildService.handleErrors(esbuildError);
+     * }
      * ```
+     *
+     * In this example, if an error occurs during the build process, the `handleErrors` method is used to
+     * process and log the errors.
      */
-    private handleDirectory;
+    private handleErrors;
     /**
-     * Handles file responses.
+     * Injects a configuration object (banner or footer) into the `esbuild` options.
+     * This method will update the `esbuild` object by adding or modifying the `banner` or `footer`
+     * property based on the provided configuration.
+     * The function handles both static values
+     * and functions within the configuration.
      *
-     * Reads and serves the content of a file.
+     * @param esbuild - The `esbuild` configuration object where the `banner` or `footer`
+     *                  should be injected or updated.
+     * @param object - The configuration object that contains the properties to inject.
+     *                 The properties can either be static values or functions.
+     * @param name - A string that determines whether the method modifies the `banner` or `footer`
+     *               property of the `esbuild` object.
      *
-     * @param fullPath - The full path to the file.
-     * @param res - The response object.
+     * @returns void - This method does not return any value.
+     * It modifies the `esbuild` object directly.
      *
-     * @example
-     * ```ts
-     * // This method is used internally to handle file responses
-     * ```
+     * @throws Error - If the `object` parameter is not provided, nothing is injected.
+     *                   No action will be taken if the specific `name` property (either
+     *                   'banner' or 'footer') does not exist in the `esbuild` object.
      */
-    private handleFile;
+    private injects;
     /**
-     * Sends a 404 Not Found response.
-     *
-     * @param res - The response object.
+     * Builds the project based on the configuration.
+     * Depending on the configuration, this method either uses esbuild's `context` for watching or `build` for a one-time build.
      *
-     * @example
-     * ```ts
-     * provider.sendNotFound(response);
-     * ```
+     * @returns A promise that resolves with the build context or result.
      *
-     * This example demonstrates how to send a 404 response using the `sendNotFound` method.
+     * @private
      */
-    private sendNotFound;
+    private build;
     /**
-     * Sends an error response.
+     * Manages development processes for specified entry points.*
+     * This method spawns development processes for each file in the metafile that matches any of the specified entry points.
+     * It enables features like source maps and optional debugging mode for each spawned process.
      *
-     * @param res - The response object.
-     * @param error - The error object.
+     * @param meta - The metafile containing information about build outputs.
+     * This typically includes a mapping of output files and their dependencies.
+     * @param entryPoint - An array of entry point file names to match against the metafile outputs.
+     * Only files that match these entry points will have development processes spawned.
+     * @param debug - A boolean flag to enable debugging mode for spawned processes.
+     * If `true`, the processes will start in debug mode with the `--inspect-brk` option. Defaults to `false`.
      *
-     * @example
-     * ```ts
-     * provider.sendError(response, new Error('Some error'));
-     * ```
-     *
-     * This example shows how to send an error response using the `sendError` method.
-     */
-    private sendError;
-}
-/**
- * Plugin provider for esbuild that registers hooks for lifecycle events such as onStart, onEnd, onResolve, and onLoad.
- * This class allows dynamic behavior by registering multiple hooks for different stages of the build process.
- */
-export declare class PluginsProvider {
-    /**
-     * Holds the build state that hooks can modify.
-     */
-    private buildState;
-    /**
-     * Holds the registered hooks for the `onEnd` lifecycle event.
-     * This array contains functions that are called after the build process completes.
-     */
-    private onEndHooks;
-    /**
-     * Holds the registered hooks for the `onSuccess` lifecycle event.
-     * This array contains functions that are called after the build success finish.
-     */
-    private onSuccess;
-    /**
-     * Holds the registered hooks for the `onLoad` lifecycle event.
-     * This array contains functions that are called when esbuild attempts to load a module.
-     */
-    private onLoadHooks;
-    /**
-     * Holds the registered hooks for the `onStart` lifecycle event.
-     * This array contains functions that are called before the build process starts.
-     */
-    private onStartHooks;
-    /**
-     * Holds the registered hooks for the `onResolve` lifecycle event.
-     * This array contains functions that are called when esbuild attempts to resolve a module path.
-     */
-    private onResolveHooks;
-    /**
-     * Registers a hook function for the `onStart` lifecycle event.
-     * The hook will be called before the build process starts.
+     * @returns void
      *
-     * @param fn - A function of type `OnStartType` that will be executed when the build process starts.
+     * @remarks
+     * - Files that contain 'map' in their names (e.g., source map files) are ignored and no process is spawned for them.
+     * - For each matching file in the metafile outputs, a new development process is spawned using the `spawn` function.
+     * - The `activePossess` array tracks all spawned processes, allowing further management (e.g., termination).
      *
      * @example
      * ```ts
-     * pluginProvider.registerOnStart(async (build) => {
-     *   console.log('Build started:', build);
-     * });
+     * const meta = {
+     *   outputs: {
+     *     'dist/index.js': { \/* ... *\/ },
+     *     'dist/index.js.map': { \/* ... *\/ }
+     *   }
+     * };
+     * const entryPoints = ['index'];
+     *
+     * this.spawnDev(meta, entryPoints, true); // Spawns processes in debug mode
      * ```
+     *
+     * @private
      */
-    registerOnStart(fn: OnStartType | undefined): void;
+    private spawnDev;
     /**
-     * Registers a hook function for the `onEnd` lifecycle event.
-     * The hook will be called after the build process completes.
-     *
-     * @param fn - A function of type `OnEndType` that will be executed after the build completes.
+     * Starts the build process and type checking.
+     * This method performs initial setup for the build and ensures that any child processes are terminated properly.
      *
-     * @example
-     * ```ts
-     * pluginProvider.registerOnEnd(async (result) => {
-     *   console.log('Build finished:', result);
-     * });
-     * ```
+     * @private
      */
-    registerOnEnd(fn: OnEndType | undefined): void;
+    private start;
     /**
-     * Registers a hook function for the `onSuccess` lifecycle event.
-     * The hook will be called after the build success completes.
-     *
-     * @param fn - A function of type `OnEndType` that will be executed after the build completes.
+     * Finalizes the build process and logs results.
+     * This method handles the end of the build process, logs build results, and processes development files if applicable.
      *
-     * @example
-     * ```ts
-     * pluginProvider.registerOnSuccess(async (result) => {
-     *   console.log('Build Success finished:', result);
-     * });
-     * ```
+     * @private
      */
-    registerOnSuccess(fn: OnEndType | undefined): void;
+    private end;
     /**
-     * Registers a hook function for the `onResolve` lifecycle event.
-     * The hook will be called when esbuild attempts to resolve a module path.
-     *
-     * @param fn - A function of type `OnResolveType` that will be executed during module resolution.
+     * Processes and updates entry points based on project dependencies.
+     * This method analyzes the project's dependencies and adjusts entry points configuration as needed.
      *
-     * @example
-     * ```ts
-     * pluginProvider.registerOnResolve(async (args) => {
-     *   if (args.path === 'my-module') {
-     *     return { path: './src/my-module.ts' };
-     *   }
-     *   return null;
-     * });
-     * ```
+     * @private
      */
-    registerOnResolve(fn: OnResolveType | undefined): void;
+    private processEntryPoints;
+}
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * The `BuildStateInterface` extends the `PluginsBuildStateInterface` interface to include additional properties related to the build
+ * process, specifically for handling `ifdef` conditions and function removals in macros.
+ *
+ * @interface BuildStateInterface
+ */
+interface BuildStateInterface extends PluginsBuildStateInterface {
+    ifdef: Array<string>;
+    macros: {
+        removeFunctions: Set<string>;
+    };
+}
+
+/**
+ * Custom error class to represent type-related errors.
+ *
+ * This class extends the built-in `Error` class to provide more specific
+ * error handling for issues related to types. It can be used to distinguish
+ * errors that occur due to type mismatches or other type-related problems
+ * in your application.
+ *
+ * @example
+ * ```ts
+ * throw new TypesError('Invalid type encountered.');
+ * ```
+ *
+ * @augments Error
+ */
+declare class TypesError extends Error {
     /**
-     * Registers a hook function for the `onLoad` lifecycle event.
-     * The hook will be called when esbuild attempts to load a module.
-     *
-     * @param fn - A function of type `OnLoadType` that will be executed during module loading.
+     * Creates an instance of `TypesError`.
      *
-     * @example
-     * ```ts
-     * pluginProvider.registerOnLoad(async (contents, loader, args) => {
-     *   if (args.path.endsWith('.json')) {
-     *     return { contents: JSON.stringify({ key: 'value' }), loader: 'json' };
-     *   }
-     *   return null;
-     * });
-     * ```
+     * @param message - A human-readable message providing details about the error.
+     * @param options - Optional configuration for the error, such as a `cause` (ECMAScript 2022+).
      */
-    registerOnLoad(fn: OnLoadType | undefined): void;
+    constructor(message?: string, options?: {
+        cause?: Error;
+    });
+}
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * Spawns a new Node.js process to execute the provided JavaScript file, with optional debugging support.
+ *
+ * This function creates a new Node.js process to run the specified JavaScript file with source map support enabled.
+ * It optionally starts the process in debug mode, which allows WebStorm or other debuggers to attach to the process.
+ * The output and error streams of the spawned process are captured and logged to the console.
+ *
+ * @param filePath - The path to the JavaScript file to execute.
+ * @param debug - A boolean flag to enable debugging. If `true`, the process will be started with the `--inspect-brk` option,
+ * which opens a debugger on `0.0.0.0:9229`, allowing external debuggers to attach.
+ *
+ * @returns A `ChildProcessWithoutNullStreams` object representing the spawned process.
+ * This object allows interaction with the process, including capturing its output and error streams.
+ *
+ * @remarks
+ * - The `--enable-source-maps` flag is used to enable source map support, which allows better debugging by mapping
+ *   errors and stack traces to the original source code.
+ * - If `debug` is `true`, the `--inspect-brk=0.0.0.0:9229` flag is added, starting the process in debug mode and pausing
+ *   execution until a debugger is attached.
+ * - The output (`stdout`) and error (`stderr`) streams of the spawned process are logged to the console.
+ * - The function returns a `ChildProcessWithoutNullStreams` object that can be used to interact with the spawned process,
+ *   such as handling its termination or sending input.
+ *
+ * @throws Error Throws an error if the Node.js process fails to start or if there are issues with the provided file path.
+ *
+ * @example
+ * ```ts
+ * import { spawn } from '@services/process.service';
+ *
+ * // Run without debugging
+ * const process = spawn('./path/to/script.js', false);
+ *
+ * process.on('close', (code) => {
+ *     console.log(`Process exited with code ${code}`);
+ * });
+ *
+ * // Run with debugging enabled
+ * const debugProcess = spawn('./path/to/script.js', true);
+ *
+ * debugProcess.on('close', (code) => {
+ *     console.log(`Debug process exited with code ${code}`);
+ * });
+ * ```
+ *
+ * In these examples, the `spawn` function is used to execute a JavaScript file, once in normal mode and once with debugging enabled.
+ * The process's exit code is logged when the process completes.
+ *
+ * @public
+ * @category Services
+ */
+declare function spawn(filePath: string, debug?: boolean): ChildProcessWithoutNullStreams;
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * The `collectFunctionNames` function analyzes the provided TypeScript code and collects the names of functions
+ * that should be removed based on specific conditions. The function searches for function declarations and variable
+ * declarations where the function name or variable is prefixed with `$$`, and adds these function names to the
+ * `removeFunctions` set in the provided `state` object.
+ *
+ * - **Input**:
+ *   - `code`: A string containing the TypeScript code to be analyzed.
+ *   - `state`: An object representing the current build state, specifically the `mocks` state, which includes
+ *     a `removeFunctions` set that will hold the names of functions that need to be removed.
+ *
+ * - **Output**: The function does not return any value. Instead, it modifies the `removeFunctions` set inside the
+ *   `state` object by adding function names that meet the criteria for removal.
+ *
+ * ## Error Handling:
+ * - The function does not explicitly handle errors. If invalid TypeScript code is provided, `ts.createSourceFile`
+ *   may throw an error, which should be handled by the caller if necessary.
+ *
+ * @param code - The TypeScript code as a string that will be analyzed.
+ * @param state - The build state containing the `removeFunctions` set to store the names of functions to be removed.
+ * @returns `void` - The function modifies the `state` directly and does not return a value.
+ */
+declare function collectFunctionNames(code: string, state: BuildStateInterface['macros']): void;
+/**
+ * The `collectDeclaredFunctions` function processes the provided `meta` metafile and reads each file's contents
+ * to find function declarations within preprocessor directives. It uses regular expressions to match `// ifdef` and
+ * `// endif` blocks in the code and collects the function names from the code inside the `ifdef` block, based on the
+ * `define` configuration in the `config` object. If the condition defined in the `ifdef` is not met (i.e., not defined
+ * in the `config.define`), the function names found inside the block will be collected and added to the `removeFunctions`
+ * set in the `state` object.
+ *
+ * - **Input**:
+ *   - `meta`: The `Metafile` object that contains the input files. The keys are file paths, and the values contain
+ *     metadata about those files.
+ *   - `config`: The configuration object containing a `define` field, which is an object of conditions that may be used
+ *     in the `ifdef` blocks. If a condition in an `ifdef` block is not defined in `config.define`, the functions in
+ *     that block will be collected.
+ *   - `state`: The build state, specifically the `mocks` state, which includes a `removeFunctions` set that stores
+ *     function names to be removed.
+ *
+ * - **Output**: This function does not return a value. It modifies the `removeFunctions` set within the provided `state`
+ *   object by adding the names of functions found inside unprocessed `ifdef` blocks.
+ *
+ * ## Error Handling:
+ * - If a file cannot be read due to a filesystem error, the function will throw an error.
+ * - If the provided `meta` or `config` is malformed, it may result in runtime errors. The caller should ensure valid input.
+ *
+ * @param meta - The `Metafile` object containing the list of input files and their metadata.
+ * @param config - The configuration object that defines conditions used in `ifdef` blocks.
+ * @param state - The build state containing the `removeFunctions` set to store function names to be removed.
+ * @returns `void` - The function modifies the `state` directly and does not return a value.
+ */
+declare function collectDeclaredFunctions(meta: Metafile, config: ConfigurationInterface, state: BuildStateInterface['macros']): Promise<void>;
+/**
+ * The `parseMacros` function processes TypeScript or JavaScript files to transform macros defined within the content.
+ * It ensures that the build state is initialized if necessary, analyzes file dependencies, collects declared functions
+ * that are marked for removal, and applies transformations to the source code based on the macros.
+ * If the file's extension is not `.ts` or `.js`, the function returns `undefined`. Otherwise, it transforms the code
+ * and returns the result in the specified loader format.
+ *
+ * - **Input**:
+ *   - `content`: The content of the file as a string or `Uint8Array` to be parsed.
+ *   - `loader`: A string representing the loader type for transforming the code (e.g., `'ts'`, `'js'`).
+ *   - `args`: The `OnLoadArgs` object containing metadata for the current loading process, including the file path.
+ *   - `state`: The build state containing the `mocks` object, which includes a `removeFunctions` set that tracks
+ *     functions to be removed.
+ *   - `config`: The configuration object that defines how macros should be handled (e.g., conditions for macro processing).
+ *
+ * - **Output**: A `Promise` that resolves to an `OnLoadResult`, `PluginResultType`, or `undefined`. If the file is
+ *   of type `.ts` or `.js`, the transformed code is returned in the specified loader format (e.g., `'ts'`). If the file
+ *   extension is not recognized, the function returns `undefined`.
+ *
+ * ## Error Handling:
+ * - If the file path does not end with `.ts` or `.js`, the function returns `undefined`.
+ * - If `state.mocks` is not initialized, it will be set up by analyzing the file dependencies and collecting declared functions.
+ * - If any errors occur during the analysis, function collection, or transformation, the function may throw an error.
+ *
+ * @param content - The content of the file as a string or `Uint8Array` to be parsed.
+ * @param loader - The loader type for transforming the code (e.g., `'ts'` or `'js'`).
+ * @param args - The `OnLoadArgs` containing metadata, including the file path.
+ * @param state - The build state that includes `mocks` with the `removeFunctions` set.
+ * @param config - The configuration object defining how macros should be handled.
+ * @returns A `Promise` that resolves to the transformed code (`OnLoadResult` or `PluginResultType`), or `undefined`
+ *          if the file is not of type `.ts` or `.js`.
+ */
+declare function parseMacros(content: string | Uint8Array, loader: Loader | undefined, args: OnLoadArgs, state: BuildStateInterface, config: ConfigurationInterface): Promise<OnLoadResult | PluginResultType | undefined>;
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * Default build options for esbuild bundler in RemoteX framework.
+ *
+ * These options are used to configure how esbuild processes and bundles the TypeScript
+ * files for the RemoteX testing framework.
+ *
+ * @public
+ * @category Configuration
+ */
+declare const defaultBuildOptions: BuildOptions;
+/**
+ * Extracts the source map from the provided data string and returns the modified code and source map separately.
+ *
+ * This function searches for the inline source map in the data string using a regular expression, removes the
+ * source map comment from the data string, and returns an object containing the code without the source map
+ * comment and the extracted source map.
+ *
+ * @param dataString - The string containing the transpiled code with an inline source map.
+ * @returns An object containing the modified code without the source map comment and the extracted source map.
+ * @throws Error -Throws an error if the source map URL is not found in the data string.
+ *
+ * @public
+ */
+declare function extractSourceMap(dataString: string): TranspileFileInterface;
+/**
+ * Transpiles a TypeScript file and extracts the source map.
+ *
+ * This function uses esbuild to transpile the specified TypeScript file based on provided build options,
+ * and then extracts the source map from the transpiled code.
+ *
+ * @param filePath - The path to the TypeScript file to be transpiled.
+ * @param buildOptions - Optional build options to override the default build options.
+ * @returns A promise that resolves to an object containing the transpiled code and the extracted source map.
+ * @throws Error - Throws an error if the build process fails or the source map extraction fails.
+ *
+ * @public
+ * @category Services
+ */
+declare function transpileFile(filePath: string, buildOptions?: BuildOptions): Promise<TranspileFileInterface>;
+/**
+ * The `analyzeDependencies` function analyzes the dependencies of a given entry point for a specified platform.
+ * It performs a bundling operation and generates a metafile that contains detailed information about the
+ * dependencies involved in the build process.
+ * This is typically used to inspect the external packages and modules
+ * that the entry point depends on.
+ *
+ * - **Input**:
+ *   - `entryPoint`: A string or array of strings representing the entry points for the build.
+ *   This defines the starting point(s) for the bundling process.
+ *   - `platform`: An optional parameter that specifies the platform to target for the build.
+ *   Default is `'browser'`.
+ *
+ * - **Output**: A `Promise` that resolves to an object containing:
+ *   - The `BuildResult` from the bundling process.
+ *   - A `metafile`, which contains detailed metadata about the build, including the dependencies analyzed.
+ *
+ * ## Example:
+ *
+ * ```ts
+ * const result = await analyzeDependencies(['src/index.ts']);
+ * console.log(result.metafile); // { inputs: { 'src/index.ts': { ... } }, outputs: { ... } }
+ *
+ * const nodeResult = await analyzeDependencies(['src/server.ts'], 'node');
+ * console.log(nodeResult.metafile); // { inputs: { 'src/server.ts': { ... } }, outputs: { ... } }
+ * ```
+ *
+ * @param entryPoint - The entry point(s) to be analyzed.
+ * @param platform - The target platform for the build.
+ * @returns A `Promise` that resolves to a `BuildResult` object along with a `metafile` containing dependency details.
+ * @throws Error If the build process fails for any reason.
+ */
+declare function analyzeDependencies(entryPoint: EntryPointsType, platform?: BuildOptions['platform']): Promise<BuildResult & {
+    metafile: Metafile;
+}>;
+
+/**
+ * Represents the result of transpiling a TypeScript file.
+ *
+ * This interface defines the structure of the output returned from a TypeScript transpilation process,
+ * including the transpiled JavaScript code and the associated source map.
+ *
+ * @property code - The transpiled JavaScript code generated from the TypeScript file.
+ * @property sourceMap - The source map associated with the transpiled JavaScript code.
+ *
+ * @remarks
+ * - The `code` property contains the JavaScript code after TypeScript transpilation.
+ * - The `sourceMap` property provides the source map that maps the transpiled JavaScript code back to the original TypeScript source.
+ * - The source map is useful for debugging as it allows developers to trace errors in the generated JavaScript back to the original TypeScript code.
+ *
+ * @example
+ * ```typescript
+ * import { TranspileFileInterface } from './TranspileFileInterface';
+ *
+ * const result: TranspileFileInterface = {
+ *     code: 'console.log("Hello, world!");',
+ *     sourceMap: 'version: 3\nfile: out.js\nsources: ["file.ts"]\n'
+ * };
+ *
+ * console.log(result.code); // Output: console.log("Hello, world!");
+ * console.log(result.sourceMap); // Output: version: 3\nfile: out.js\nsources: ["file.ts"]\n
+ * ```
+ *
+ * In this example, the `TranspileFileInterface` is used to represent the result of transpiling a TypeScript file.
+ * The `code` contains the JavaScript code, while the `sourceMap` provides the mapping information for debugging purposes.
+ *
+ * @public
+ * @category Interfaces
+ */
+interface TranspileFileInterface {
+    code: string;
+    sourceMap: string;
+}
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * Represents an error that occurs during the esbuild process.
+ *
+ * This class extends the base error class to provide specific error handling for esbuild-related issues.
+ * It captures the error message and maintains the proper stack trace, allowing for easier debugging
+ * and identification of errors that occur during the build process.
+ *
+ * @class esBuildError
+ * @extends BaseError
+ */
+declare class esBuildError extends BaseError {
+    originalErrorStack?: string;
     /**
-     * Registers esbuild plugin hooks and sets up the middleware plugin.
-     *
-     * This function defines the setup for an esbuild plugin, enabling hooks for various lifecycle events:
-     * onStart, onEnd, onResolve, and onLoad. It ensures that hooks registered by the user are called at
-     * the appropriate stages of the build process.
-     *
-     * @returns An object with the plugin configuration that can be passed to esbuild's `plugins` array.
-     * The configuration includes the plugin name and setup function.
-     *
-     * @example
-     * ```ts
-     * // Example usage with esbuild:
-     * const esbuild = require('esbuild');
-     * const pluginProvider = new PluginsProvider();
+     * Creates an instance of the EsbuildError class.
      *
-     * esbuild.build({
-     *   entryPoints: ['./src/index.ts'],
-     *   bundle: true,
-     *   plugins: [pluginProvider.setup()],
-     * }).catch(() => process.exit(1));
-     * ```
+     * @param message - An object containing the error message. The `text` property is used to initialize
+     * the base error class with a descriptive message about the error encountered during the esbuild process.
      */
-    setup(): Plugin;
+    constructor(message: Message);
     /**
-     * Executes all registered onStart hooks.
-     *
-     * This function is called when the build process starts and invokes each hook registered via
-     * `registerOnStart`. Hooks can perform actions such as initializing tasks, logging, or setting
-     * up build conditions.
-     *
-     * @param build - The esbuild `PluginBuild` object that represents the current build process.
-     *
-     * @returns A promise that resolves when all hooks have been executed.
+     * Generates a formatted error message with highlighted code.
      *
-     * @example
-     * ```ts
-     * // Registering an onStart hook
-     * pluginProvider.registerOnStart(async (build) => {
-     *   console.log('Build started:', build);
-     * });
-     * ```
+     * @param message - An esbuild Message object containing error information.
+     * @returns A formatted string of the error message.
      */
-    private handleOnStart;
+    private generateFormattedError;
     /**
-     * Executes all registered onEnd hooks after the build finishes.
-     *
-     * This function is called after the build process completes and invokes each hook registered via
-     * `registerOnEnd`. Hooks can be used to process the build results, such as performing analysis or cleanup.
-     *
-     * @param buildResult - The build buildResult object provided by esbuild, containing details about the build process.
-     *
-     * @returns A promise that resolves when all hooks have been executed.
+     * Reads code from a file if it exists.
      *
-     * @example
-     * ```ts
-     * // Registering an onEnd hook
-     * pluginProvider.registerOnEnd(async (buildResult) => {
-     *   console.log('Build completed:', buildResult);
-     * });
-     * ```
+     * @param path - The file path to read from.
+     * @returns Array of lines if file exists, otherwise null.
      */
-    private handleOnEnd;
+    private readCode;
     /**
-     * Resolves module imports using registered onResolve hooks.
-     *
-     * This function is called whenever esbuild attempts to resolve a module path. It iterates over all registered
-     * onResolve hooks and merges their results. If no hook resolves a path, `null` is returned.
-     *
-     * @param args - The esbuild `OnResolveArgs` object containing information about the module being resolved.
-     *
-     * @returns A promise that resolves to an `OnResolveResult` containing the resolved path, or `null` if no path is found.
+     * Formats a code snippet with highlighted errors.
      *
-     * @example
-     * ```ts
-     * // Registering an onResolve hook
-     * pluginProvider.registerOnResolve(async (args) => {
-     *   if (args.path === 'my-module') {
-     *     return { path: './src/my-module.ts' };
-     *   }
-     *   return null;
-     * });
-     * ```
+     * @param code - Array of code lines.
+     * @param location - The error location within the file.
+     * @returns A formatted and highlighted code snippet string.
      */
-    private handleOnResolve;
+    private formatCodeSnippet;
     /**
-     * Loads module contents using registered onLoad hooks.
-     *
-     * This function is called when esbuild attempts to load a module. It reads the module contents and then
-     * processes it through all registered onLoad hooks. The hooks can modify the contents and loader type.
-     *
-     * @param args - The esbuild `OnLoadArgs` object containing information about the module being loaded.
-     *
-     * @returns A promise that resolves to an `OnLoadResult` containing the module contents and loader, or `null` if no contents are loaded.
+     * Applies color to a given text if colors are enabled.
      *
-     * @example
-     * ```ts
-     * // Registering an onLoad hook
-     * pluginProvider.registerOnLoad(async (contents, loader, args) => {
-     *   if (args.path.endsWith('.json')) {
-     *     return { contents: JSON.stringify({ key: 'value' }), loader: 'json' };
-     *   }
-     *   return null;
-     * });
-     * ```
+     * @param color - The color code.
+     * @param text - The text to colorize.
+     * @returns The colorized text if colors are active, otherwise plain text.
      */
-    private handleOnLoad;
+    private applyColor;
 }
+
 /**
- * Parses and filters content based on conditional directives.
- *
- * This function processes the given code contents and removes sections that
- * are conditionally compiled based on the provided `defines` object.
- *
- * @param contents - The code contents to be processed.
- * @param defines - An object containing conditional
- *   definitions. Keys are condition names, and values are their definitions.
- * @returns The processed code contents with conditional blocks removed
- *   according to the `defines` object.
+ * Imports
  */
-export declare function parseIfDefConditionals(contents: string, defines: Record<string, unknown>): string;
 /**
- * Represents the result of a TypeScript compilation emit operation.
- *
- * @property outputFile - The emitted output file information,
- *   or undefined if no file was emitted. Contains details such as file name, content,
- *   and any related metadata.
- *
- * @property emitSkipped - Indicates whether the emit operation was skipped.
- *   When true, typically indicates compilation errors prevented emission or the operation
- *   was explicitly configured to skip emission.
+ * ASCII Logo and Version Information
  *
  * @remarks
- * This interface is used to represent the result of TypeScript declaration emit operations.
+ * The `asciiLogo` constant stores an ASCII representation of the project logo
+ * that will be displayed in the banner. This banner is rendered in a formatted
+ * string in the `bannerComponent` function.
  *
- * @since 1.5.9
+ * The `cleanScreen` constant contains an ANSI escape code to clear the terminal screen.
  */
-export interface EmitOutputInterface {
-    outputFile: OutputFile | undefined;
-    emitSkipped: boolean;
-}
+declare const asciiLogo = "\n     ______       _ _     _\n     | ___ \\     (_) |   | |\n__  _| |_/ /_   _ _| | __| |\n\\ \\/ / ___ \\ | | | | |/ _` |\n >  <| |_/ / |_| | | | (_| |\n/_/\\_\\____/ \\__,_|_|_|\\__,_|\n";
+declare const cleanScreen = "\u001Bc";
 /**
- * A host object that provides formatting functionality for typescript diagnostic messages
+ * Renders the banner with the ASCII logo and version information.
  *
- * @remarks
- * This constant implements the FormatDiagnosticsHost interface from TypeScript,
- * providing methods needed for proper diagnostic message formatting.
+ * This function constructs and returns a formatted banner string that includes an ASCII logo and the version number.
+ * The colors used for the ASCII logo and version number can be enabled or disabled based on the `activeColor` parameter.
+ * If color formatting is enabled, the ASCII logo will be rendered in burnt orange, and the version number will be in bright pink.
  *
- * @default Uses TypeScript's system utilities for line breaks and directory information
+ * @param activeColor - A boolean flag indicating whether ANSI color formatting should be applied. Default is `__ACTIVE_COLOR`.
  *
- * @see FormatDiagnosticsHost - The TypeScript interface this implements
+ * @returns A formatted string containing the ASCII logo, version number, and ANSI color codes if `activeColor` is `true`.
  *
- * @since 1.5.9
- */
-export declare const formatHost: FormatDiagnosticsHost;
-/**
- * Header text included at the top of generated declaration bundle files
+ * @remarks
+ * The `bannerComponent` function clears the terminal screen, applies color formatting if enabled, and displays
+ * the ASCII logo and version number. The version number is retrieved from the global `__VERSION` variable, and
+ * the colors are reset after the text is rendered.
  *
- * @remarks
- * This constant provides a standardized header comment that prepended to all
- * declaration bundle files generated by the DeclarationBundlerService. The header
- * clearly indicates that the file was automatically generated and should not be
- * edited manually.
+ * @example
+ * ```ts
+ * console.log(bannerComponent());
+ * ```
+ *
+ * This will output the banner to the console with the ASCII logo, version, and colors.
  *
  * @example
  * ```ts
- * const bundledContent = `${HeaderDeclarationBundle}${actualContent}`;
- * writeFileSync('dist/index.d.ts', bundledContent);
+ * console.log(bannerComponent(false));
  * ```
  *
- * @since 1.5.9
+ * This will output the banner to the console with the ASCII logo and version number without color formatting.
+ *
+ * @public
  */
-export declare const HeaderDeclarationBundle = "\n/**\n * This file was automatically generated by xBuild.\n * DO NOT EDIT MANUALLY.\n */\n ";
+declare function bannerComponent(activeColor?: boolean): string;
 /**
- * Service that implements TypeScript's language service host interfaces required for compiler operations.
- * This class provides the necessary methods for the TypeScript language service to interact with the
- * file system and manage compilation resources.
- *
- * @remarks
- * This service implements the TypeScript LanguageServiceHost interface, which is required
- * for creating a TypeScript language service using ts.createLanguageService().
+ * A formatted string prefix used for logging build-related messages.
+ * // todo optimize this
+ */
+declare function prefix(): string;
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * Manages the HTTP or HTTPS server based on the provided configuration.
  *
- * @see ts.LanguageServiceHost
- * @see ts.createLanguageService
+ * The `ServerProvider` class initializes and starts either an HTTP or HTTPS server based on whether SSL certificates
+ * are provided. It handles incoming requests, serves static files, and lists directory contents with appropriate
+ * icons and colors.
  *
- * @since 1.5.9
+ * @class
  */
-export declare class LanguageHostService {
-    private readonly options;
+declare class ServerProvider {
     /**
-     * Map to track file versions for detecting changes in source files.
-     * Keys are absolute file paths and values are incrementing version numbers.
-     *
-     * @since 1.5.9
+     * Root dir to serve
      */
-    private readonly fileVersions;
+    private readonly rootDir;
     /**
-     * Creates a new language host service with TypeScript compiler options.
-     *
-     * @param options - Compiler options to use for TypeScript operations
-     *
-     * @since 1.5.9
+     * Indicates whether the server is configured to use HTTPS.
      */
-    constructor(options: CompilerOptions);
+    private readonly isHttps;
     /**
-     * Increments the version number of a file to indicate it has changed.
-     * Used to signal to the language service that a file needs to be reprocessed.
-     *
-     * @param touchFiles - Path to the file that has been modified
-     *
-     * @since 1.5.9
+     * The server configuration object, including SSL certificate paths and other settings.
      */
-    touchFiles(touchFiles: string): void;
+    private readonly config;
     /**
-     * Checks if a file exists at the specified path.
-     * Required by the LanguageServiceHost interface.
+     * Creates an instance of ServerProvider.
      *
-     * @param path - Path to check for file existence
-     * @returns True if the file exists, false otherwise
+     * @param config - The server configuration object, including port number, SSL certificate paths, and an optional request handler.
+     * @param dir - The root directory from which to serve files.
      *
-     * @see ts.LanguageServiceHost.fileExists
-     * @since 1.5.9
-     */
-    fileExists(path: string): boolean;
-    /**
-     * Reads the content of a file at the specified path.
-     * Required by the LanguageServiceHost interface.
+     * @example
+     * ```ts
+     * import { ServerProvider } from './server-provider';
      *
-     * @param path - Path to the file to read
-     * @param encoding - Optional encoding to use when reading the file
-     * @returns The content of the file as a string, or undefined if the file cannot be read
+     * const serverConfig = {
+     *     port: 8080,
+     *     keyfile: './path/to/keyfile',
+     *     certfile: './path/to/certfile',
+     *     onRequest: (req, res, next) => { /* custom request handling *\/ }
+     * };
+     * const provider = new ServerProvider(serverConfig, './public');
+     * provider.start();
+     * ```
      *
-     * @see ts.LanguageServiceHost.readFile
-     * @since 1.5.9
+     * This example shows how to create an instance of `ServerProvider` and start the server.
      */
-    readFile(path: string, encoding?: string): string | undefined;
+    constructor(config: ServeInterface, dir: string);
     /**
-     * Reads the contents of a directory with filtering options.
-     * Required by the LanguageServiceHost interface.
+     * Starts the server based on the configuration.
+     * If SSL certificates are provided and valid, an HTTPS server is started. Otherwise, an HTTP server is started.
      *
-     * @param path - Path to the directory to read
-     * @param extensions - Optional array of file extensions to filter by
-     * @param exclude - Optional array of glob patterns to exclude
-     * @param include - Optional array of glob patterns to include
-     * @param depth - Optional maximum depth to search
-     * @returns Array of file paths found in the directory
+     * @example
+     * ```ts
+     * provider.start();
+     * ```
      *
-     * @see ts.LanguageServiceHost.readDirectory
-     * @since 1.5.9
+     * This example demonstrates how to start the server. It will either start an HTTP or HTTPS server based on the configuration.
      */
-    readDirectory(path: string, extensions?: Array<string>, exclude?: Array<string>, include?: Array<string>, depth?: number): Array<string>;
+    start(): void;
     /**
-     * Gets all subdirectories within a directory.
-     * Required by the LanguageServiceHost interface.
+     * Starts an HTTP server.
+     * This method creates an HTTP server that listens on the configured port and handles incoming requests.
      *
-     * @param path - Path to the directory to search
-     * @returns Array of directory paths found
+     * @example
+     * ```ts
+     * provider.startHttpServer();
+     * ```
      *
-     * @see ts.LanguageServiceHost.getDirectories
-     * @since 1.5.9
+     * This example shows how the `startHttpServer` method is used internally to start an HTTP server.
      */
-    getDirectories(path: string): Array<string>;
+    private startHttpServer;
     /**
-     * Checks if a directory exists at the specified path.
-     *
-     * @param path - Path to check for directory existence
-     * @returns True if the directory exists, false otherwise
+     * Starts an HTTPS server.
      *
-     * @since 1.5.9
-     */
-    directoryExists(path: string): boolean;
-    /**
-     * Gets the current working directory.
-     * Required by the LanguageServiceHost interface.
+     * This method creates an HTTPS server with SSL/TLS certificates, listens on the configured port, and handles incoming requests.
      *
-     * @returns The current working directory path
+     * @example
+     * ```ts
+     * provider.startHttpsServer();
+     * ```
      *
-     * @see ts.LanguageServiceHost.getCurrentDirectory
-     * @since 1.5.9
+     * This example shows how the `startHttpsServer` method is used internally to start an HTTPS server.
      */
-    getCurrentDirectory(): string;
+    private startHttpsServer;
     /**
-     * Gets all script file names tracked by this language host.
-     * Required by the LanguageServiceHost interface to identify the set of source files.
-     *
-     * @returns Array of script file paths that should be included in the program
+     * Handles incoming requests.
      *
-     * @see ts.LanguageServiceHost.getScriptFileNames
-     * @since 1.5.9
-     */
-    getScriptFileNames(): Array<string>;
-    /**
-     * Gets the compiler options used by this language host.
-     * Required by the LanguageServiceHost interface to configure the TypeScript compiler.
+     * This method checks if a custom request handler is provided in the configuration. If so, it uses the custom handler.
+     * Otherwise, it delegates to the default request handler.
      *
-     * @returns The compiler options for program creation
+     * @param req - The incoming request object.
+     * @param res - The response object.
+     * @param defaultHandler - The default handler functions to be called if no custom handler is provided.
      *
-     * @see ts.LanguageServiceHost.getCompilationSettings
-     * @since 1.5.9
+     * @example
+     * ```ts
+     * // This method is used internally to handle requests
+     * ```
      */
-    getCompilationSettings(): CompilerOptions;
+    private handleRequest;
     /**
-     * Gets the default library file name for TypeScript compilation.
-     * Required by the LanguageServiceHost interface to include standard TypeScript definitions.
-     *
-     * @param options - Compiler options to use for determining the default library
-     * @returns Path to the default library file
+     * Returns the MIME type for a given file extension.
      *
-     * @see ts.LanguageServiceHost.getDefaultLibFileName
-     * @since 1.5.9
-     */
-    getDefaultLibFileName(options: CompilerOptions): string;
-    /**
-     * Gets the current version of a script file.
-     * Required by the LanguageServiceHost interface to determine if a file has changed.
+     * This method maps file extensions to their corresponding MIME types.
      *
-     * @param fileName - Path to the script file
-     * @returns The version of the file as a string
+     * @param ext - The file extension.
+     * @returns The MIME type associated with the file extension.
      *
-     * @see ts.LanguageServiceHost.getScriptVersion
-     * @since 1.5.9
+     * @example
+     * ```ts
+     * const mimeType = provider.getContentType('html');
+     * console.log(mimeType); // 'text/html'
+     * ```
      */
-    getScriptVersion(fileName: string): string;
+    private getContentType;
     /**
-     * Gets a script snapshot for a file which represents its content.
-     * Required by the LanguageServiceHost interface to provide file content to the language service.
+     * Handles the default response for requests, serving files or directories.
      *
-     * @param fileName - Path to the script file
-     * @returns A script snapshot object or undefined if the file doesn't exist or can't be read
+     * This method serves the content of files or directories. If the request is for a directory, it lists the contents with
+     * appropriate icons and colors.
      *
-     * @see ts.LanguageServiceHost.getScriptSnapshot
-     * @see ts.IScriptSnapshot
-     * @since 1.5.9
-     */
-    getScriptSnapshot(fileName: string): IScriptSnapshot | undefined;
-}
-/**
- * Service responsible for bundling TypeScript declaration files by collecting
- * all exports from entry points and generating a single declaration bundle
- *
- * @throws Error - If the language service program is not available
- * @throws Error - If a source file cannot be found
- *
- * @remarks
- * This service handles the process of bundling TypeScript declaration files (.d.ts)
- * by traversing the dependency graph starting from specified entry points.
- * It collects all necessary files and symbols, processes their declarations,
- * and generates a single bundled declaration file that can be used in place
- * of multiple individual declaration files.
- *
- * The service maintains a cache of processed files to improve performance
- * when processing multiple entry points or when called multiple times.
- *
- * @example
- * ```ts
- * const bundler = new DeclarationBundlerService(config, languageService);
- * const bundledDeclarations = bundler.emitBundledDeclarations(['src/index.ts']);
- * writeFileSync('dist/index.d.ts', bundledDeclarations[0]);
- * ```
- *
- * @see ts.LanguageService
- * @see ts.ParsedCommandLine
- *
- * @since 1.5.9
- */
-export declare class DeclarationBundlerService {
-    private readonly config;
-    private readonly languageService;
-    /**
-     * Cache of processed declaration files to avoid redundant processing
+     * @param req - The incoming request object.
+     * @param res - The response object.
      *
-     * @since 1.5.9
-     */
-    private readonly processedFiles;
-    /**
-     * Creates a new DeclarationBundlerService instance
+     * @returns A promise that resolves when the response is sent.
      *
-     * @param config - TypeScript configuration with compiler options
-     * @param languageService - TypeScript language service for compilation
+     * @throws  Throws an error if the file or directory cannot be accessed.
      *
-     * @since 1.5.9
+     * @example
+     * ```ts
+     * // This method is used internally to handle file and directory responses
+     * ```
      */
-    constructor(config: ParsedCommandLine, languageService: LanguageService);
+    private defaultResponse;
     /**
-     * Generates bundled declaration files for the provided entry points
+     * promisifyStat the `fs.stat` method.
      *
-     * @param entryPoints - Array of file paths to use as entry points
-     * @returns Array of bundled declaration content strings
+     * Converts the `fs.stat` callback-based method to return a promise.
      *
-     * @remarks
-     * This method clears any existing cache and processes each entry point
-     * to generate bundled declarations. Entry points should be absolute paths
-     * to TypeScript source files.
+     * @param path - The file or directory path.
+     * @returns A promise that resolves with the file statistics.
      *
-     * @since 1.5.9
+     * @example
+     * ```ts
+     * const stats = await provider.promisifyStat('./path/to/file');
+     * console.log(stats.isFile()); // true or false
+     * ```
      */
-    emitBundledDeclarations(entryPoints: Array<string>): Array<string>;
+    private promisifyStat;
     /**
-     * Generates a bundled declaration for a single entry point
+     * Handles directory listings.
      *
-     * @param entryPath - Path to the entry point file
-     * @returns Bundled declaration content or undefined if generation fails
+     * Reads the contents of a directory and generates an HTML response with file icons and colors.
      *
-     * @throws EntryPointError - When the specified entry point file cannot be found
-     * @throws CompilationError - When the TypeScript program cannot be accessed
+     * @param fullPath - The full path to the directory.
+     * @param requestPath - The request path for generating relative links.
+     * @param res - The response object.
      *
-     * @remarks
-     * This method processes a single entry point to generate a bundled declaration file.
-     * It collects all necessary files and exported symbols, processes them, and
-     * combines them into a single declaration output.
+     * @example
+     * ```ts
+     * // This method is used internally to handle directory listings
+     * ```
+     */
+    private handleDirectory;
+    /**
+     * Handles file responses.
      *
-     * The method requires that the entry point file exists and is included in the
-     * TypeScript project configuration.
+     * Reads and serves the content of a file.
      *
-     * @since 1.5.9
+     * @param fullPath - The full path to the file.
+     * @param res - The response object.
+     *
+     * @example
+     * ```ts
+     * // This method is used internally to handle file responses
+     * ```
      */
-    private generateBundledDeclaration;
+    private handleFile;
     /**
-     * Resolves a module name to its file path
+     * Sends a 404 Not Found response.
      *
-     * @param moduleName - The module name to resolve
-     * @param containingFile - The file containing the import
-     * @param program - The TypeScript program
+     * @param res - The response object.
      *
-     * @returns The resolved file path or undefined if resolution fails
+     * @example
+     * ```ts
+     * provider.sendNotFound(response);
+     * ```
      *
-     * @since 1.5.9
+     * This example demonstrates how to send a 404 response using the `sendNotFound` method.
      */
-    private resolveModule;
+    private sendNotFound;
     /**
-     * Recursively collects all files by following imports and exports
+     * Sends an error response.
      *
-     * @param sourceFile - The source file to process
-     * @param program - The TypeScript program
-     * @param collectedFiles - Set of collected file paths
+     * @param res - The response object.
+     * @param error - The error object.
      *
-     * @remarks
-     * This method traverses the dependency graph starting from the provided source file
-     * and collects all files that contribute to the final bundle, excluding node_modules.
+     * @example
+     * ```ts
+     * provider.sendError(response, new Error('Some error'));
+     * ```
      *
-     * @since 1.5.9
+     * This example shows how to send an error response using the `sendError` method.
      */
-    private collectFilesRecursive;
+    private sendError;
+}
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * Plugin provider for esbuild that registers hooks for lifecycle events such as onStart, onEnd, onResolve, and onLoad.
+ * This class allows dynamic behavior by registering multiple hooks for different stages of the build process.
+ */
+declare class PluginsProvider {
     /**
-     * Recursively collects exports from a module symbol
-     *
-     * @param symbol - The module symbol to process
-     * @param checker - The TypeScript type checker
-     * @param collectedSymbols - Set of collected symbol names
+     * Holds the build state that hooks can modify.
+     */
+    private buildState;
+    /**
+     * Holds the registered hooks for the `onEnd` lifecycle event.
+     * This array contains functions that are called after the build process completes.
+     */
+    private onEndHooks;
+    /**
+     * Holds the registered hooks for the `onSuccess` lifecycle event.
+     * This array contains functions that are called after the build success finish.
+     */
+    private onSuccess;
+    /**
+     * Holds the registered hooks for the `onLoad` lifecycle event.
+     * This array contains functions that are called when esbuild attempts to load a module.
+     */
+    private onLoadHooks;
+    /**
+     * Holds the registered hooks for the `onStart` lifecycle event.
+     * This array contains functions that are called before the build process starts.
+     */
+    private onStartHooks;
+    /**
+     * Holds the registered hooks for the `onResolve` lifecycle event.
+     * This array contains functions that are called when esbuild attempts to resolve a module path.
+     */
+    private onResolveHooks;
+    /**
+     * Registers a hook function for the `onStart` lifecycle event.
+     * The hook will be called before the build process starts.
      *
-     * @remarks
-     * This method collects all exported symbols from a module, including
-     * nested module exports for namespace declarations.
+     * @param fn - A function of type `OnStartType` that will be executed when the build process starts.
      *
-     * @since 1.5.9
+     * @example
+     * ```ts
+     * pluginProvider.registerOnStart(async (build) => {
+     *   console.log('Build started:', build);
+     * });
+     * ```
      */
-    private collectExportsRecursive;
+    registerOnStart(fn: OnStartType | undefined): void;
     /**
-     * Processes all collected files and extracts their declarations
+     * Registers a hook function for the `onEnd` lifecycle event.
+     * The hook will be called after the build process completes.
      *
-     * @param collectedFiles - Set of file paths to process
-     * @param collectedSymbols - Set of exported symbol names
-     * @returns Object containing bundled content and external imports
+     * @param fn - A function of type `OnEndType` that will be executed after the build completes.
      *
-     * @since 1.5.9
+     * @example
+     * ```ts
+     * pluginProvider.registerOnEnd(async (result) => {
+     *   console.log('Build finished:', result);
+     * });
+     * ```
      */
-    private processDeclaredFiles;
+    registerOnEnd(fn: OnEndType | undefined): void;
     /**
-     * Collects all exported symbols from a source file
+     * Registers a hook function for the `onSuccess` lifecycle event.
+     * The hook will be called after the build success completes.
      *
-     * @param sourceFile - The source file to process
-     * @param checker - The TypeScript type checker
-     * @param collectedSymbols - Set to store collected symbol names
+     * @param fn - A function of type `OnEndType` that will be executed after the build completes.
      *
-     * @since 1.5.9
+     * @example
+     * ```ts
+     * pluginProvider.registerOnSuccess(async (result) => {
+     *   console.log('Build Success finished:', result);
+     * });
+     * ```
      */
-    private collectExportsFromSourceFile;
+    registerOnSuccess(fn: OnEndType | undefined): void;
     /**
-     * Processes a declaration file to extract its content
+     * Registers a hook function for the `onResolve` lifecycle event.
+     * The hook will be called when esbuild attempts to resolve a module path.
      *
-     * @param fileName - Path to the declaration file
-     * @param collectedSymbols - Set of exported symbol names
-     * @param externalImports - Set to store external import statements
-     * @returns Processed declaration content or undefined if processing fails
+     * @param fn - A function of type `OnResolveType` that will be executed during module resolution.
      *
-     * @remarks
-     * This method processes a single declaration file, filtering its content
-     * to include only relevant declarations and collecting external imports.
-     * It uses a cache to avoid reprocessing the same file multiple times.
+     * @example
+     * ```ts
+     * pluginProvider.registerOnResolve(async (args) => {
+     *   if (args.path === 'my-module') {
+     *     return { path: './src/my-module.ts' };
+     *   }
+     *   return null;
+     * });
+     * ```
+     */
+    registerOnResolve(fn: OnResolveType | undefined): void;
+    /**
+     * Registers a hook function for the `onLoad` lifecycle event.
+     * The hook will be called when esbuild attempts to load a module.
      *
-     * @since 1.5.9
+     * @param fn - A function of type `OnLoadType` that will be executed during module loading.
+     *
+     * @example
+     * ```ts
+     * pluginProvider.registerOnLoad(async (contents, loader, args) => {
+     *   if (args.path.endsWith('.json')) {
+     *     return { contents: JSON.stringify({ key: 'value' }), loader: 'json' };
+     *   }
+     *   return null;
+     * });
+     * ```
      */
-    private processDeclarationFile;
+    registerOnLoad(fn: OnLoadType | undefined): void;
     /**
-     * Checks if a line is an import or export statement with a from clause
+     * Registers esbuild plugin hooks and sets up the middleware plugin.
      *
-     * @param line - The line to check
-     * @returns True if the line is an import or export with from clause
+     * This function defines the setup for an esbuild plugin, enabling hooks for various lifecycle events:
+     * onStart, onEnd, onResolve, and onLoad. It ensures that hooks registered by the user are called at
+     * the appropriate stages of the build process.
      *
-     * @since 1.5.9
+     * @returns An object with the plugin configuration that can be passed to esbuild's `plugins` array.
+     * The configuration includes the plugin name and setup function.
+     *
+     * @example
+     * ```ts
+     * // Example usage with esbuild:
+     * const esbuild = require('esbuild');
+     * const pluginProvider = new PluginsProvider();
+     *
+     * esbuild.build({
+     *   entryPoints: ['./src/index.ts'],
+     *   bundle: true,
+     *   plugins: [pluginProvider.setup()],
+     * }).catch(() => process.exit(1));
+     * ```
      */
-    private isImportOrExportWithFrom;
+    setup(): Plugin;
     /**
-     * Extracts the module path from an import or export statement
+     * Executes all registered onStart hooks.
      *
-     * @param line - The import or export statement
-     * @returns The extracted module path or undefined if not found
+     * This function is called when the build process starts and invokes each hook registered via
+     * `registerOnStart`. Hooks can perform actions such as initializing tasks, logging, or setting
+     * up build conditions.
      *
-     * @since 1.5.9
+     * @param build - The esbuild `PluginBuild` object that represents the current build process.
+     *
+     * @returns A promise that resolves when all hooks have been executed.
+     *
+     * @example
+     * ```ts
+     * // Registering an onStart hook
+     * pluginProvider.registerOnStart(async (build) => {
+     *   console.log('Build started:', build);
+     * });
+     * ```
      */
-    private extractModulePath;
+    private handleOnStart;
     /**
-     * Determines if a module is external (from node_modules)
+     * Executes all registered onEnd hooks after the build finishes.
      *
-     * @param modulePath - The module path to check
-     * @param fileName - The file containing the import
-     * @returns True if the module is external
+     * This function is called after the build process completes and invokes each hook registered via
+     * `registerOnEnd`. Hooks can be used to process the build results, such as performing analysis or cleanup.
      *
-     * @remarks
-     * This method determines if a module is external by checking if it's a relative
-     * or absolute path, and by resolving the module to see if it's in node_modules.
+     * @param buildResult - The build buildResult object provided by esbuild, containing details about the build process.
      *
-     * @since 1.5.9
+     * @returns A promise that resolves when all hooks have been executed.
+     *
+     * @example
+     * ```ts
+     * // Registering an onEnd hook
+     * pluginProvider.registerOnEnd(async (buildResult) => {
+     *   console.log('Build completed:', buildResult);
+     * });
+     * ```
      */
-    private isExternalModule;
+    private handleOnEnd;
     /**
-     * Processes an export line, removing 'export' if needed
+     * Resolves module imports using registered onResolve hooks.
      *
-     * @param line - The export statement to process
-     * @param collectedSymbols - Set of exported symbol names
-     * @returns The processed line
+     * This function is called whenever esbuild attempts to resolve a module path. It iterates over all registered
+     * onResolve hooks and merges their results. If no hook resolves a path, `null` is returned.
      *
-     * @remarks
-     * This method processes an export declaration line, removing the 'export'
-     * keyword if the symbol is not in the collected exports.
+     * @param args - The esbuild `OnResolveArgs` object containing information about the module being resolved.
      *
-     * @since 1.5.9
+     * @returns A promise that resolves to an `OnResolveResult` containing the resolved path, or `null` if no path is found.
+     *
+     * @example
+     * ```ts
+     * // Registering an onResolve hook
+     * pluginProvider.registerOnResolve(async (args) => {
+     *   if (args.path === 'my-module') {
+     *     return { path: './src/my-module.ts' };
+     *   }
+     *   return null;
+     * });
+     * ```
      */
-    private processExportLine;
+    private handleOnResolve;
     /**
-     * Creates the final bundled declaration content
+     * Loads module contents using registered onLoad hooks.
      *
-     * @param externalImports - Set of external import statements
-     * @param bundledContent - Array of processed declaration content
-     * @returns The final bundled declaration content
+     * This function is called when esbuild attempts to load a module. It reads the module contents and then
+     * processes it through all registered onLoad hooks. The hooks can modify the contents and loader type.
      *
-     * @since 1.5.9
+     * @param args - The esbuild `OnLoadArgs` object containing information about the module being loaded.
+     *
+     * @returns A promise that resolves to an `OnLoadResult` containing the module contents and loader, or `null` if no contents are loaded.
+     *
+     * @example
+     * ```ts
+     * // Registering an onLoad hook
+     * pluginProvider.registerOnLoad(async (contents, loader, args) => {
+     *   if (args.path.endsWith('.json')) {
+     *     return { contents: JSON.stringify({ key: 'value' }), loader: 'json' };
+     *   }
+     *   return null;
+     * });
+     * ```
      */
-    private createFinalBundleContent;
+    private handleOnLoad;
 }
+
+/**
+ * Parses and filters content based on conditional directives.
+ *
+ * This function processes the given code contents and removes sections that
+ * are conditionally compiled based on the provided `defines` object.
+ *
+ * @param contents - The code contents to be processed.
+ * @param defines - An object containing conditional
+ *   definitions. Keys are condition names, and values are their definitions.
+ * @returns The processed code contents with conditional blocks removed
+ *   according to the `defines` object.
+ */
+declare function parseIfDefConditionals(contents: string, defines: Record<string, unknown>): string;
+
+/**
+ * Import will remove at compile time
+ */
 /**
  * Manages TypeScript compilation, type checking, and declaration file generation using TypeScript's
  * language service API.
@@ -2041,7 +2165,7 @@ export declare class DeclarationBundlerService {
  *
  * @since 1.5.9
  */
-export declare class TypescriptModule {
+declare class TypescriptModule {
     /**
      * The root directory of the TypeScript project.
      * @since 1.5.9
@@ -2322,518 +2446,590 @@ export declare class TypescriptModule {
      */
     private getDiagnostics;
 }
+
 /**
- * Resolves path aliases in the provided content based on the specified paths and root directory.
- *
- * This function takes a string of content and replaces occurrences of defined path alias keys
- * with their corresponding relative paths derived from the specified source file and root directory.
- * It ensures that the resulting paths are relative to the directory of the source file and formatted
- * correctly for use in a JavaScript/TypeScript environment.
- *
- * Example:
- * Given the following inputs:
- * ```ts
- * const content = "import { foo } from '@core/foo';";
- * const sourceFile = "/project/src/index.ts";
- * const paths = {
- *   '@core/': 'src/core',
- *   '@utils/': 'src/utils'
- * };
- * const rootDir = "/project";
- * ```
- * The function will replace `@core/foo` with a relative path based on the source file's location,
- * potentially resulting in:
- * ```ts
- * const content = "import { foo } from './core/foo';";
- * ```
- *
- * @param content - The content in which path aliases need to be resolved.
- * @param sourceFile - The path of the source file from which relative paths will be calculated.
- * @param paths - An object mapping path alias keys to their corresponding paths.
- * @param esm -  A flag indicating whether ESM is enabled.
- * @returns The updated content with resolved path aliases.
+ * Import will remove at compile time
  */
-export declare function resolveAliasPlugin(content: string, sourceFile: string, paths: Record<string, string>, esm: boolean): string;
 /**
- * Maps an array of file paths to an object where the keys are filenames (without extensions)
- * and the values are the corresponding file paths.
+ * Represents the result of a TypeScript compilation emit operation.
  *
- * Each key in the resulting object is derived from the filename by removing the file extension.
- * For example, given a file path `src/index.ts`, the key in the resulting object will be `src/index`.
+ * @property outputFile - The emitted output file information,
+ *   or undefined if no file was emitted. Contains details such as file name, content,
+ *   and any related metadata.
  *
- * @param filePaths - An array of file paths to map. Each file path should be a string.
- * @returns An object where the keys are filenames (without extensions) and the values are the corresponding file paths.
+ * @property emitSkipped - Indicates whether the emit operation was skipped.
+ *   When true, typically indicates compilation errors prevented emission or the operation
+ *   was explicitly configured to skip emission.
  *
- * @example
- * ```ts
- * const filePaths = ['src/index.ts', 'src/utils.ts'];
- * const result = mapFilePathsToNames(filePaths);
- * console.log(result);
- * // Output: {
- * //   'src/index': 'src/index.ts',
- * //   'src/utils': 'src/utils.ts'
- * // }
- * ```
+ * @remarks
+ * This interface is used to represent the result of TypeScript declaration emit operations.
+ *
+ * @since 1.5.9
  */
-export declare function mapFilePathsToNames(filePaths: Array<string>): Record<string, string>;
+interface EmitOutputInterface {
+    outputFile: OutputFile | undefined;
+    emitSkipped: boolean;
+}
+
 /**
- * Extracts and returns an object mapping output file paths to input file paths from the provided `EntryPointsType` object.
- *
- * This function handles multiple formats of entry points, including:
- * - An array of strings representing file paths.
- * - An array of objects containing `in` and `out` properties, where `in` is the input file path and `out` is the output file path.
- * - A `Record<string, string>` where the keys represent input file paths and the values represent output file paths.
- *
- * Depending on the format, the function constructs an object with the output file paths as keys and the input file paths as values.
- * If the output path is not available, the filename (without extension) is used as the key.
+ * Import will remove at compile time
+ */
+/**
+ * A host object that provides formatting functionality for typescript diagnostic messages
  *
- * If a regular object with string keys and values (not in the supported formats) is provided, it will be returned as is.
+ * @remarks
+ * This constant implements the FormatDiagnosticsHost interface from TypeScript,
+ * providing methods needed for proper diagnostic message formatting.
  *
- * @param entryPoints - The entry points to extract from, which can be in different formats: an array of strings,
- * an array of objects with `in` and `out` properties, or a `Record<string, string>`.
+ * @default Uses TypeScript's system utilities for line breaks and directory information
  *
- * @returns An object mapping output file paths to input file paths, or filename (without extension) to file path.
+ * @see FormatDiagnosticsHost - The TypeScript interface this implements
  *
- * @throws Will throw an `Error` if the entry points format is unsupported.
+ * @since 1.5.9
+ */
+declare const formatHost: FormatDiagnosticsHost;
+/**
+ * Header text included at the top of generated declaration bundle files
  *
- * @example
- * ```ts
- * const entryPoints = extractEntryPoints(['src/index.ts', 'src/utils.ts']);
- * console.log(entryPoints); // { 'index': 'src/index.ts', 'utils': 'src/utils.ts' }
- * ```
+ * @remarks
+ * This constant provides a standardized header comment that prepended to all
+ * declaration bundle files generated by the DeclarationBundlerService. The header
+ * clearly indicates that the file was automatically generated and should not be
+ * edited manually.
  *
  * @example
  * ```ts
- * const entryPoints = extractEntryPoints([{ in: 'src/index.ts', out: 'dist/index.js' }]);
- * console.log(entryPoints); // { 'dist/index.js': 'src/index.ts' }
+ * const bundledContent = `${HeaderDeclarationBundle}${actualContent}`;
+ * writeFileSync('dist/index.d.ts', bundledContent);
  * ```
  *
- * @example
- * ```ts
- * const entryPoints = extractEntryPoints({ index: 'src/index.ts', index2: 'dist/index2.js' });
- * console.log(entryPoints); // { index: 'src/index.ts', index2: 'dist/index2.js' }
- * ```
+ * @since 1.5.9
  */
-export declare function extractEntryPoints(entryPoints: EntryPointsType): Record<string, string>;
+declare const HeaderDeclarationBundle = "\n/**\n * This file was automatically generated by xBuild.\n * DO NOT EDIT MANUALLY.\n */\n ";
+
 /**
- * Generates a `package.json` file with the appropriate `type` field
- * based on the format specified in the configuration.
- *
- * - If the format is `esm`, the `type` will be set to `"module"`.
- * - If the format is `cjs`, the `type` will be set to `"commonjs"`.
- *
- * The function will ensure that the specified output directory exists, and if it doesn't,
- * it will create the necessary directories before writing the `package.json` file.
- *
- * @param config - The build configuration object containing
- * esbuild-related settings, such as the format (`format`).
- *
- * - `config.esbuild.format`: The module format, either `'esm'` or `'cjs'`, that determines the `type` field.
- *
- * @throws Will throw an error if there is a problem creating the directory or writing the file.
- *
- * Example usage:
- *
- * ```ts
- * const config = {
- *   esbuild: {
- *     format: 'esm'
- *   }
- * };
- * packageTypeComponent(config);
- * // This will create 'dist/package.json' with the content: {"type": "module"}
- * ```
+ * Import will remove at compile time
  */
-export declare function packageTypeComponent(config: ConfigurationInterface): void;
 /**
- * Manages the build process for a TypeScript project using esbuild.
- *
- * The `BuildService` class orchestrates the build process, including TypeScript compilation, handling of build errors,
- * and lifecycle management of the build. It can operate in various modes, such as watching for file changes or running
- * in development mode. It also provides functionality for spawning development processes and processing entry points.
+ * Service that implements TypeScript's language service host interfaces required for compiler operations.
+ * This class provides the necessary methods for the TypeScript language service to interact with the
+ * file system and manage compilation resources.
  *
  * @remarks
- * - The build process can be configured using the provided `ConfigurationInterface`.
- * - Errors related to TypeScript are handled separately and are not logged by default.
- * - The class supports various build modes, including watch mode and development mode, and handles different scenarios
- *   based on the configuration.
+ * This service implements the TypeScript LanguageServiceHost interface, which is required
+ * for creating a TypeScript language service using ts.createLanguageService().
  *
- * @public
- * @category Services
+ * @see ts.LanguageServiceHost
+ * @see ts.createLanguageService
+ *
+ * @since 1.5.9
  */
-export declare class BuildService {
-    private config;
+declare class LanguageHostService {
+    private readonly options;
     /**
-     * Provides TypeScript-related functionality for the build process.
+     * Map to track file versions for detecting changes in source files.
+     * Keys are absolute file paths and values are incrementing version numbers.
+     *
+     * @since 1.5.9
      */
-    readonly typescriptModule: TypescriptModule;
+    private readonly fileVersions;
     /**
-     * Keeps track of active development processes spawned during the build.
-     * This property holds an array of `ChildProcessWithoutNullStreams` instances that represent Node.js processes spawned
-     * for running development tasks. These processes are used to handle development builds or runtime tasks and are managed
-     * by the `BuildService` class to ensure they are properly started and stopped.
+     * Creates a new language host service with TypeScript compiler options.
      *
-     * @remarks
-     * - The array is populated when development processes are spawned, such as when specific development files are
-     *   processed or when running in development mode.
-     * - The processes are terminated gracefully at the end of the build to avoid leaving orphaned processes running.
-     * - It is important to manage these processes correctly to avoid resource leaks and ensure proper cleanup.
+     * @param options - Compiler options to use for TypeScript operations
      *
-     * @see ChildProcessWithoutNullStreams
+     * @since 1.5.9
      */
-    private activePossess;
+    constructor(options: CompilerOptions);
     /**
-     * Plugin provider
+     * Increments the version number of a file to indicate it has changed.
+     * Used to signal to the language service that a file needs to be reprocessed.
      *
-     * @private
+     * @param touchFiles - Path to the file that has been modified
+     *
+     * @since 1.5.9
      */
-    private pluginsProvider;
+    touchFiles(touchFiles: string): void;
     /**
-     * A mapping of output filenames to their corresponding source file paths.
+     * Checks if a file exists at the specified path.
+     * Required by the LanguageServiceHost interface.
      *
-     * @remarks
-     * This property stores the entry points configuration for TypeScript compilation.
-     * - Keys represent the output filenames (with or without .d.ts extension)
-     * - Values represent the source file paths to use as entry points
+     * @param path - Path to check for file existence
+     * @returns True if the file exists, false otherwise
      *
-     * Used by declaration bundling operations to determine which files to process
-     * and how to name the resulting declaration outputs.
+     * @see ts.LanguageServiceHost.fileExists
+     * @since 1.5.9
+     */
+    fileExists(path: string): boolean;
+    /**
+     * Reads the content of a file at the specified path.
+     * Required by the LanguageServiceHost interface.
      *
-     * @example
-     * ```ts
-     * // Example entryPoints structure
-     * {
-     *   'index': 'src/index.ts',
-     *   'components/button': 'src/components/button.ts'
-     * }
-     * ```
+     * @param path - Path to the file to read
+     * @param encoding - Optional encoding to use when reading the file
+     * @returns The content of the file as a string, or undefined if the file cannot be read
      *
-     * @private
+     * @see ts.LanguageServiceHost.readFile
      * @since 1.5.9
      */
-    private readonly entryPoints;
+    readFile(path: string, encoding?: string): string | undefined;
     /**
-     * Initializes the build service with the provided configuration.
+     * Reads the contents of a directory with filtering options.
+     * Required by the LanguageServiceHost interface.
      *
-     * The constructor configures the TypeScript provider, suppresses esbuild logging,
-     * sets up development modes, and registers the necessary plugins.
+     * @param path - Path to the directory to read
+     * @param extensions - Optional array of file extensions to filter by
+     * @param exclude - Optional array of glob patterns to exclude
+     * @param include - Optional array of glob patterns to include
+     * @param depth - Optional maximum depth to search
+     * @returns Array of file paths found in the directory
      *
-     * Declaration files will be output based on the following order of precedence:
-     * 1. If `declarationOutDir` is set in the configuration, it will be used.
-     * 2. If `declarationOutDir` is not provided, it will use the `outDir` value from the tsconfig.
-     * 3. If neither of the above is available, it falls back to using the `outdir` specified in the esbuild configuration.
+     * @see ts.LanguageServiceHost.readDirectory
+     * @since 1.5.9
+     */
+    readDirectory(path: string, extensions?: Array<string>, exclude?: Array<string>, include?: Array<string>, depth?: number): Array<string>;
+    /**
+     * Gets all subdirectories within a directory.
+     * Required by the LanguageServiceHost interface.
      *
-     * @param config - The configuration object for the build process, including esbuild and TypeScript settings.
+     * @param path - Path to the directory to search
+     * @returns Array of directory paths found
+     *
+     * @see ts.LanguageServiceHost.getDirectories
+     * @since 1.5.9
      */
-    constructor(config: ConfigurationInterface);
+    getDirectories(path: string): Array<string>;
     /**
-     * Executes the build process.
-     * This method performs the build and handles any errors that occur during the execution.
-     * If watching or development mode is enabled in the configuration, it starts watching for changes
-     * to automatically rebuild as needed.
-     * The method logs errors that are not related to TypeScript
-     * compilation issues.
+     * Checks if a directory exists at the specified path.
      *
-     * @returns A promise that resolves with a `BuildResult` when the build process is complete,
-     *          or `undefined` if an error occurs during execution.
+     * @param path - Path to check for directory existence
+     * @returns True if the directory exists, false otherwise
      *
-     * @throws Error Throws an error if the build process encounters issues that are not related
-     *                 to TypeScript. Such errors are logged, but the method does not rethrow them.
+     * @since 1.5.9
+     */
+    directoryExists(path: string): boolean;
+    /**
+     * Gets the current working directory.
+     * Required by the LanguageServiceHost interface.
      *
-     * @example
-     * ```ts
-     * import { BuildService } from './build-service';
+     * @returns The current working directory path
      *
-     * const buildService = new BuildService(config);
-     * buildService.run().then(() => {
-     *     console.log('Build process completed successfully.');
-     * }).catch((error) => {
-     *     console.error('Build process failed:', error);
-     * });
-     * ```
+     * @see ts.LanguageServiceHost.getCurrentDirectory
+     * @since 1.5.9
+     */
+    getCurrentDirectory(): string;
+    /**
+     * Gets all script file names tracked by this language host.
+     * Required by the LanguageServiceHost interface to identify the set of source files.
+     *
+     * @returns Array of script file paths that should be included in the program
+     *
+     * @see ts.LanguageServiceHost.getScriptFileNames
+     * @since 1.5.9
+     */
+    getScriptFileNames(): Array<string>;
+    /**
+     * Gets the compiler options used by this language host.
+     * Required by the LanguageServiceHost interface to configure the TypeScript compiler.
+     *
+     * @returns The compiler options for program creation
+     *
+     * @see ts.LanguageServiceHost.getCompilationSettings
+     * @since 1.5.9
+     */
+    getCompilationSettings(): CompilerOptions;
+    /**
+     * Gets the default library file name for TypeScript compilation.
+     * Required by the LanguageServiceHost interface to include standard TypeScript definitions.
+     *
+     * @param options - Compiler options to use for determining the default library
+     * @returns Path to the default library file
+     *
+     * @see ts.LanguageServiceHost.getDefaultLibFileName
+     * @since 1.5.9
+     */
+    getDefaultLibFileName(options: CompilerOptions): string;
+    /**
+     * Gets the current version of a script file.
+     * Required by the LanguageServiceHost interface to determine if a file has changed.
+     *
+     * @param fileName - Path to the script file
+     * @returns The version of the file as a string
+     *
+     * @see ts.LanguageServiceHost.getScriptVersion
+     * @since 1.5.9
+     */
+    getScriptVersion(fileName: string): string;
+    /**
+     * Gets a script snapshot for a file which represents its content.
+     * Required by the LanguageServiceHost interface to provide file content to the language service.
+     *
+     * @param fileName - Path to the script file
+     * @returns A script snapshot object or undefined if the file doesn't exist or can't be read
+     *
+     * @see ts.LanguageServiceHost.getScriptSnapshot
+     * @see ts.IScriptSnapshot
+     * @since 1.5.9
+     */
+    getScriptSnapshot(fileName: string): IScriptSnapshot | undefined;
+}
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * Service responsible for bundling TypeScript declaration files by collecting
+ * all exports from entry points and generating a single declaration bundle
+ *
+ * @throws Error - If the language service program is not available
+ * @throws Error - If a source file cannot be found
+ *
+ * @remarks
+ * This service handles the process of bundling TypeScript declaration files (.d.ts)
+ * by traversing the dependency graph starting from specified entry points.
+ * It collects all necessary files and symbols, processes their declarations,
+ * and generates a single bundled declaration file that can be used in place
+ * of multiple individual declaration files.
+ *
+ * The service maintains a cache of processed files to improve performance
+ * when processing multiple entry points or when called multiple times.
+ *
+ * @example
+ * ```ts
+ * const bundler = new DeclarationBundlerService(config, languageService);
+ * const bundledDeclarations = bundler.emitBundledDeclarations(['src/index.ts']);
+ * writeFileSync('dist/index.d.ts', bundledDeclarations[0]);
+ * ```
+ *
+ * @see ts.LanguageService
+ * @see ts.ParsedCommandLine
+ *
+ * @since 1.5.9
+ */
+declare class DeclarationBundlerService {
+    private readonly config;
+    private readonly languageService;
+    /**
+     * Cache of processed declaration files to avoid redundant processing
+     *
+     * @since 1.5.9
+     */
+    private readonly processedFiles;
+    /**
+     * Creates a new DeclarationBundlerService instance
+     *
+     * @param config - TypeScript configuration with compiler options
+     * @param languageService - TypeScript language service for compilation
+     *
+     * @since 1.5.9
+     */
+    constructor(config: ParsedCommandLine, languageService: LanguageService);
+    /**
+     * Generates bundled declaration files for the provided entry points
+     *
+     * @param entryPoints - Array of file paths to use as entry points
+     * @returns Array of bundled declaration content strings
+     *
+     * @remarks
+     * This method clears any existing cache and processes each entry point
+     * to generate bundled declarations. Entry points should be absolute paths
+     * to TypeScript source files.
      *
-     * In this example, the `run` method is invoked to execute the build process. It handles both successful
-     * completion and logs any encountered errors, allowing the user to understand the outcome of the build.
+     * @since 1.5.9
      */
-    run(): Promise<BuildResult | void>;
+    emitBundledDeclarations(entryPoints: Array<string>): Array<string>;
     /**
-     * Runs the build process in debug mode for the specified entry points.
-     * This method temporarily disables development and watch mode, initiates the build process, and spawns development processes
-     * for the specified entry points. If any errors occur during the build, they are handled appropriately.
-     *
-     * @param entryPoints - An array of entry point file names for which the development processes will be spawned.
-     * These entry points are matched against the build output files.
+     * Generates a bundled declaration for a single entry point
      *
-     * @returns A `Promise<void>` that resolves when the build and process spawning have completed.
+     * @param entryPath - Path to the entry point file
+     * @returns Bundled declaration content or undefined if generation fails
      *
-     * @throws Handles any build-related errors using the `handleErrors` method.
+     * @throws EntryPointError - When the specified entry point file cannot be found
+     * @throws CompilationError - When the TypeScript program cannot be accessed
      *
      * @remarks
-     * - The `config.dev` and `config.watch` settings are temporarily disabled to prevent development mode or file watching during the build.
-     * - The `build()` method is called to generate the necessary build outputs.
-     * - The `spawnDev` method is then invoked to spawn processes for the matching entry points.
-     * - If any errors occur during the build, they are caught and passed to the `handleErrors` method.
-     *
-     * @example
-     * ```ts
-     * const entryPoints = ['index', 'main'];
-     * await this.runDebug(entryPoints);
-     * ```
+     * This method processes a single entry point to generate a bundled declaration file.
+     * It collects all necessary files and exported symbols, processes them, and
+     * combines them into a single declaration output.
      *
-     * In this example, the `runDebug` method runs the build process and spawns development processes for `index` and `main`.
+     * The method requires that the entry point file exists and is included in the
+     * TypeScript project configuration.
      *
-     * @public
+     * @since 1.5.9
      */
-    runDebug(entryPoints: Array<string>): Promise<void>;
+    private generateBundledDeclaration;
     /**
-     * Serves the project and watches for changes.
-     * This method starts the development server using the `ServerProvider`, builds the project using esbuild,
-     * and watches for file changes to automatically rebuild as needed. It initializes the server and invokes
-     * the build process, enabling continuous development mode.
-     *
-     * @returns A promise that resolves when the server is started and the build process is complete.
+     * Resolves a module name to its file path
      *
-     * @throws This method catches any errors thrown during the build process and handles them using the
-     * `handleErrors` method.
+     * @param moduleName - The module name to resolve
+     * @param containingFile - The file containing the import
+     * @param program - The TypeScript program
      *
-     * @example
-     * ```ts
-     * const buildService = new BuildService(config);
-     * buildService.serve().then(() => {
-     *     console.log('Server is running and watching for changes.');
-     * }).catch((error) => {
-     *     console.error('Failed to start the server:', error);
-     * });
-     * ```
+     * @returns The resolved file path or undefined if resolution fails
      *
-     * In this example, the `serve` method starts the server and watches for changes. If an error occurs during
-     * the build or server startup, it is handled and logged.
+     * @since 1.5.9
      */
-    serve(): Promise<void>;
+    private resolveModule;
     /**
-     * Executes a provided asynchronous callback function within a try-catch block.
-     * This method ensures that any errors thrown during the execution of the callback
-     * are properly handled and logged. If the error appears to be an `esbuild`-related
-     * `OnEndResult` error with an array of errors, it avoids redundant logging.
-     * Otherwise, it wraps the error in a `VMRuntimeError` and logs the stack trace.
-     *
-     * @template T - The return type of the callback function, allowing flexibility
-     *               in the expected result type. Defaults to `BuildResult`.
-     *
-     * @param callback - A function that returns a `Promise<T>`, which is executed asynchronously.
-     *                   The callback is wrapped in error handling logic to catch and process any exceptions.
+     * Recursively collects all files by following imports and exports
      *
-     * @returns A `Promise<T | void>` that resolves with the result of the callback function if successful,
-     *          or `void` if an error was thrown and handled. This allows for optional chaining on the return value.
+     * @param sourceFile - The source file to process
+     * @param program - The TypeScript program
+     * @param collectedFiles - Set of collected file paths
      *
-     * @throws This method does not throw explicitly but will log an error message if an exception is caught
-     *         and is not an `esbuild`-related error. The error stack is logged via `VMRuntimeError` for non-esbuild errors.
+     * @remarks
+     * This method traverses the dependency graph starting from the provided source file
+     * and collects all files that contribute to the final bundle, excluding node_modules.
      *
-     * @example
-     * ```ts
-     * await execute(async () => {
-     *   // Perform some asynchronous operation here
-     *   return someResult;
-     * });
-     * ```
-     */
-    private execute;
-    /**
-     * Configures the development mode by ensuring that `config.dev` is set properly.
+     * @since 1.5.9
      */
-    private configureDevelopmentMode;
+    private collectFilesRecursive;
     /**
-     * Sets up the plugin's provider and registers the plugin HooksInterface.
+     * Recursively collects exports from a module symbol
+     *
+     * @param symbol - The module symbol to process
+     * @param checker - The TypeScript type checker
+     * @param collectedSymbols - Set of collected symbol names
+     *
+     * @remarks
+     * This method collects all exported symbols from a module, including
+     * nested module exports for namespace declarations.
+     *
+     * @since 1.5.9
      */
-    private setupPlugins;
+    private collectExportsRecursive;
     /**
-     * Registers the plugin HooksInterface for start, end, and load events.
+     * Processes all collected files and extracts their declarations
      *
-     * @param paths - The resolved path aliases.
-     * @param rootDir - The root directory for resolving paths.
+     * @param collectedFiles - Set of file paths to process
+     * @param collectedSymbols - Set of exported symbol names
+     * @returns Object containing bundled content and external imports
+     *
+     * @since 1.5.9
      */
-    private registerPluginHooks;
+    private processDeclaredFiles;
     /**
-     * Generates a path alias object from the TypeScript provider's path options.
-     * This method processes the `paths` property from the TypeScript provider's options,
-     * which is expected to be an object where each key represents a path alias pattern,
-     * and the corresponding value is an array of paths. The method removes any wildcard
-     * characters (`*`) from both the keys and the first values of the arrays. It also
-     * resolves the paths relative to the specified `rootDir`, returning a simplified
-     * object that maps the cleaned keys to their respective paths.
-     *
-     * The resolved paths will be formatted to use a relative path notation.
+     * Collects all exported symbols from a source file
      *
-     * Example:
-     * Given the following paths:
-     * ```ts
-     * {
-     *   '@core/*': ['src/core/*'],
-     *   '@utils/*': ['src/utils/*']
-     * }
-     * ```
-     * And assuming `rootDir` is set to the base directory of your project, the method
-     * will return:
-     * ```ts
-     * {
-     *   '@core/': './core/',
-     *   '@utils/': './utils/'
-     * }
-     * ```
+     * @param sourceFile - The source file to process
+     * @param checker - The TypeScript type checker
+     * @param collectedSymbols - Set to store collected symbol names
      *
-     * @param rootDir - The root directory to resolve paths against.
-     * @returns An object mapping cleaned path aliases to their respective resolved paths.
+     * @since 1.5.9
      */
-    private generatePathAlias;
+    private collectExportsFromSourceFile;
     /**
-     * Handles errors during the build process.
-     * This method processes and logs errors that occur during the esbuild process. It specifically filters out
-     * errors related to TypeScript (`TypesError`) to prevent them from being logged, while logging all other errors
-     * to the console. The error object is assumed to contain a list of messages, each with detailed information.
-     *
-     * @param esbuildError - The error object returned by esbuild, which is expected to contain an array of
-     * error messages.
+     * Processes a declaration file to extract its content
      *
-     * @private
+     * @param fileName - Path to the declaration file
+     * @param collectedSymbols - Set of exported symbol names
+     * @param externalImports - Set to store external import statements
+     * @returns Processed declaration content or undefined if processing fails
      *
      * @remarks
-     * - TypeScript errors (denoted as `TypesError`) are skipped and not logged.
-     * - Other errors are logged to the console with their text descriptions.
-     *
-     * @example
-     * ```ts
-     * try {
-     *     await buildService.run();
-     * } catch (esbuildError) {
-     *     buildService.handleErrors(esbuildError);
-     * }
-     * ```
+     * This method processes a single declaration file, filtering its content
+     * to include only relevant declarations and collecting external imports.
+     * It uses a cache to avoid reprocessing the same file multiple times.
      *
-     * In this example, if an error occurs during the build process, the `handleErrors` method is used to
-     * process and log the errors.
+     * @since 1.5.9
      */
-    private handleErrors;
+    private processDeclarationFile;
     /**
-     * Injects a configuration object (banner or footer) into the `esbuild` options.
-     * This method will update the `esbuild` object by adding or modifying the `banner` or `footer`
-     * property based on the provided configuration.
-     * The function handles both static values
-     * and functions within the configuration.
-     *
-     * @param esbuild - The `esbuild` configuration object where the `banner` or `footer`
-     *                  should be injected or updated.
-     * @param object - The configuration object that contains the properties to inject.
-     *                 The properties can either be static values or functions.
-     * @param name - A string that determines whether the method modifies the `banner` or `footer`
-     *               property of the `esbuild` object.
+     * Checks if a line is an import or export statement with a from clause
      *
-     * @returns void - This method does not return any value.
-     * It modifies the `esbuild` object directly.
+     * @param line - The line to check
+     * @returns True if the line is an import or export with from clause
      *
-     * @throws Error - If the `object` parameter is not provided, nothing is injected.
-     *                   No action will be taken if the specific `name` property (either
-     *                   'banner' or 'footer') does not exist in the `esbuild` object.
+     * @since 1.5.9
      */
-    private injects;
+    private isImportOrExportWithFrom;
     /**
-     * Builds the project based on the configuration.
-     * Depending on the configuration, this method either uses esbuild's `context` for watching or `build` for a one-time build.
+     * Extracts the module path from an import or export statement
      *
-     * @returns A promise that resolves with the build context or result.
+     * @param line - The import or export statement
+     * @returns The extracted module path or undefined if not found
      *
-     * @private
+     * @since 1.5.9
      */
-    private build;
+    private extractModulePath;
     /**
-     * Manages development processes for specified entry points.*
-     * This method spawns development processes for each file in the metafile that matches any of the specified entry points.
-     * It enables features like source maps and optional debugging mode for each spawned process.
-     *
-     * @param meta - The metafile containing information about build outputs.
-     * This typically includes a mapping of output files and their dependencies.
-     * @param entryPoint - An array of entry point file names to match against the metafile outputs.
-     * Only files that match these entry points will have development processes spawned.
-     * @param debug - A boolean flag to enable debugging mode for spawned processes.
-     * If `true`, the processes will start in debug mode with the `--inspect-brk` option. Defaults to `false`.
+     * Determines if a module is external (from node_modules)
      *
-     * @returns void
+     * @param modulePath - The module path to check
+     * @param fileName - The file containing the import
+     * @returns True if the module is external
      *
      * @remarks
-     * - Files that contain 'map' in their names (e.g., source map files) are ignored and no process is spawned for them.
-     * - For each matching file in the metafile outputs, a new development process is spawned using the `spawn` function.
-     * - The `activePossess` array tracks all spawned processes, allowing further management (e.g., termination).
-     *
-     * @example
-     * ```ts
-     * const meta = {
-     *   outputs: {
-     *     'dist/index.js': { \/* ... *\/ },
-     *     'dist/index.js.map': { \/* ... *\/ }
-     *   }
-     * };
-     * const entryPoints = ['index'];
-     *
-     * this.spawnDev(meta, entryPoints, true); // Spawns processes in debug mode
-     * ```
+     * This method determines if a module is external by checking if it's a relative
+     * or absolute path, and by resolving the module to see if it's in node_modules.
      *
-     * @private
+     * @since 1.5.9
      */
-    private spawnDev;
+    private isExternalModule;
     /**
-     * Starts the build process and type checking.
-     * This method performs initial setup for the build and ensures that any child processes are terminated properly.
+     * Processes an export line, removing 'export' if needed
      *
-     * @private
-     */
-    private start;
-    /**
-     * Finalizes the build process and logs results.
-     * This method handles the end of the build process, logs build results, and processes development files if applicable.
+     * @param line - The export statement to process
+     * @param collectedSymbols - Set of exported symbol names
+     * @returns The processed line
      *
-     * @private
+     * @remarks
+     * This method processes an export declaration line, removing the 'export'
+     * keyword if the symbol is not in the collected exports.
+     *
+     * @since 1.5.9
      */
-    private end;
+    private processExportLine;
     /**
-     * Processes and updates entry points based on project dependencies.
-     * This method analyzes the project's dependencies and adjusts entry points configuration as needed.
+     * Creates the final bundled declaration content
      *
-     * @private
+     * @param externalImports - Set of external import statements
+     * @param bundledContent - Array of processed declaration content
+     * @returns The final bundled declaration content
+     *
+     * @since 1.5.9
      */
-    private processEntryPoints;
+    private createFinalBundleContent;
 }
+
 /**
- * Executes JavaScript code within a sandboxed environment using Node.js's `vm` module.
+ * Imports
+ */
+/**
+ * Resolves path aliases in the provided content based on the specified paths and root directory.
  *
- * @param code - The JavaScript code to be executed within the sandbox.
- * @param sandbox - An optional context object to be used as the global scope for the executed code.
+ * This function takes a string of content and replaces occurrences of defined path alias keys
+ * with their corresponding relative paths derived from the specified source file and root directory.
+ * It ensures that the resulting paths are relative to the directory of the source file and formatted
+ * correctly for use in a JavaScript/TypeScript environment.
  *
- * @returns The result of executing the provided code within the sandboxed environment.
+ * Example:
+ * Given the following inputs:
+ * ```ts
+ * const content = "import { foo } from '@core/foo';";
+ * const sourceFile = "/project/src/index.ts";
+ * const paths = {
+ *   '@core/': 'src/core',
+ *   '@utils/': 'src/utils'
+ * };
+ * const rootDir = "/project";
+ * ```
+ * The function will replace `@core/foo` with a relative path based on the source file's location,
+ * potentially resulting in:
+ * ```ts
+ * const content = "import { foo } from './core/foo';";
+ * ```
  *
- * @remarks
- * The `sandboxExecute` function creates a new `Script` instance with the provided code and
- * runs it within a sandboxed context using the `createContext` function from the `vm` module.
- * This approach ensures that the executed code is isolated from the rest of the application,
- * mitigating potential security risks.
+ * @param content - The content in which path aliases need to be resolved.
+ * @param sourceFile - The path of the source file from which relative paths will be calculated.
+ * @param paths - An object mapping path alias keys to their corresponding paths.
+ * @param esm -  A flag indicating whether ESM is enabled.
+ * @returns The updated content with resolved path aliases.
+ */
+declare function resolveAliasPlugin(content: string, sourceFile: string, paths: Record<string, string>, esm: boolean): string;
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * Maps an array of file paths to an object where the keys are filenames (without extensions)
+ * and the values are the corresponding file paths.
  *
- * The `sandbox` parameter allows you to provide a custom context or global object for the
- * sandboxed code. If not provided, an empty context is used. The function also supports
- * breaking execution on interrupt signals (e.g., Ctrl+C) with the `breakOnSigint` option.
+ * Each key in the resulting object is derived from the filename by removing the file extension.
+ * For example, given a file path `src/index.ts`, the key in the resulting object will be `src/index`.
  *
- * @throws Error Throws an error if the code cannot be compiled or executed within the context.
+ * @param filePaths - An array of file paths to map. Each file path should be a string.
+ * @returns An object where the keys are filenames (without extensions) and the values are the corresponding file paths.
  *
  * @example
  * ```ts
- * const result = sandboxExecute('return 2 + 2;', { myGlobal: 10 });
- * console.log(result); // Output: 4
+ * const filePaths = ['src/index.ts', 'src/utils.ts'];
+ * const result = mapFilePathsToNames(filePaths);
+ * console.log(result);
+ * // Output: {
+ * //   'src/index': 'src/index.ts',
+ * //   'src/utils': 'src/utils.ts'
+ * // }
  * ```
+ */
+declare function mapFilePathsToNames(filePaths: Array<string>): Record<string, string>;
+/**
+ * Extracts and returns an object mapping output file paths to input file paths from the provided `EntryPointsType` object.
  *
- * In this example, the `sandboxExecute` function runs a simple JavaScript expression and returns
- * the result. The `sandbox` parameter is provided with an empty object in this case.
+ * This function handles multiple formats of entry points, including:
+ * - An array of strings representing file paths.
+ * - An array of objects containing `in` and `out` properties, where `in` is the input file path and `out` is the output file path.
+ * - A `Record<string, string>` where the keys represent input file paths and the values represent output file paths.
  *
- * @public
- * @category Services
+ * Depending on the format, the function constructs an object with the output file paths as keys and the input file paths as values.
+ * If the output path is not available, the filename (without extension) is used as the key.
+ *
+ * If a regular object with string keys and values (not in the supported formats) is provided, it will be returned as is.
+ *
+ * @param entryPoints - The entry points to extract from, which can be in different formats: an array of strings,
+ * an array of objects with `in` and `out` properties, or a `Record<string, string>`.
+ *
+ * @returns An object mapping output file paths to input file paths, or filename (without extension) to file path.
+ *
+ * @throws Will throw an `Error` if the entry points format is unsupported.
+ *
+ * @example
+ * ```ts
+ * const entryPoints = extractEntryPoints(['src/index.ts', 'src/utils.ts']);
+ * console.log(entryPoints); // { 'index': 'src/index.ts', 'utils': 'src/utils.ts' }
+ * ```
+ *
+ * @example
+ * ```ts
+ * const entryPoints = extractEntryPoints([{ in: 'src/index.ts', out: 'dist/index.js' }]);
+ * console.log(entryPoints); // { 'dist/index.js': 'src/index.ts' }
+ * ```
+ *
+ * @example
+ * ```ts
+ * const entryPoints = extractEntryPoints({ index: 'src/index.ts', index2: 'dist/index2.js' });
+ * console.log(entryPoints); // { index: 'src/index.ts', index2: 'dist/index2.js' }
+ * ```
+ */
+declare function extractEntryPoints(entryPoints: EntryPointsType): Record<string, string>;
+
+/**
+ * Import will remove at compile time
+ */
+/**
+ * Generates a `package.json` file with the appropriate `type` field
+ * based on the format specified in the configuration.
+ *
+ * - If the format is `esm`, the `type` will be set to `"module"`.
+ * - If the format is `cjs`, the `type` will be set to `"commonjs"`.
+ *
+ * The function will ensure that the specified output directory exists, and if it doesn't,
+ * it will create the necessary directories before writing the `package.json` file.
+ *
+ * @param config - The build configuration object containing
+ * esbuild-related settings, such as the format (`format`).
+ *
+ * - `config.esbuild.format`: The module format, either `'esm'` or `'cjs'`, that determines the `type` field.
+ *
+ * @throws Will throw an error if there is a problem creating the directory or writing the file.
+ *
+ * Example usage:
+ *
+ * ```ts
+ * const config = {
+ *   esbuild: {
+ *     format: 'esm'
+ *   }
+ * };
+ * packageTypeComponent(config);
+ * // This will create 'dist/package.json' with the content: {"type": "module"}
+ * ```
+ */
+declare function packageTypeComponent(config: ConfigurationInterface): void;
+
+/**
+ * Import will remove at compile time
  */
-export declare function sandboxExecute(code: string, sandbox?: Context): unknown;
 /**
  * Parses a configuration file and returns a wrapped `ConfigurationInterface` object.
  *
@@ -2850,30 +3046,54 @@ export declare function sandboxExecute(code: string, sandbox?: Context): unknown
  *
  * @throws Will throw an error if the transpilation or execution of the configuration file fails.
  * The thrown error will have sourcemap information attached if available.
-
  * @example
  * ```ts
  * const config = await parseConfigurationFile('./config.jet.ts');
  * console.log(config);
  * ```
  */
-export declare function parseConfigurationFile(file: string): Promise<ConfigurationInterface>;
+declare function parseConfigurationFile(file: string): Promise<ConfigurationInterface>;
+
+/**
+ * Import will remove at compile time
+ */
 /**
- * The default configuration options for the build.
+ * Executes JavaScript code within a sandboxed environment using Node.js's `vm` module.
+ *
+ * @param code - The JavaScript code to be executed within the sandbox.
+ * @param sandbox - An optional context object to be used as the global scope for the executed code.
+ *
+ * @returns The result of executing the provided code within the sandboxed environment.
+ *
+ * @remarks
+ * The `sandboxExecute` function creates a new `Script` instance with the provided code and
+ * runs it within a sandboxed context using the `createContext` function from the `vm` module.
+ * This approach ensures that the executed code is isolated from the rest of the application,
+ * mitigating potential security risks.
+ *
+ * The `sandbox` parameter allows you to provide a custom context or global object for the
+ * sandboxed code. If not provided, an empty context is used. The function also supports
+ * breaking execution on interrupt signals (e.g., Ctrl+C) with the `breakOnSigint` option.
+ *
+ * @throws Error Throws an error if the code cannot be compiled or executed within the context.
  *
  * @example
  * ```ts
- * import { defaultConfiguration } from '@configuration/default-configuration';
- *
- * console.log(defaultConfiguration);
+ * const result = sandboxExecute('return 2 + 2;', { myGlobal: 10 });
+ * console.log(result); // Output: 4
  * ```
  *
- * In this example, the `defaultConfiguration` is imported and logged to the console to view the default settings.
+ * In this example, the `sandboxExecute` function runs a simple JavaScript expression and returns
+ * the result. The `sandbox` parameter is provided with an empty object in this case.
  *
  * @public
- * @category Configuration
+ * @category Services
+ */
+declare function sandboxExecute(code: string, sandbox?: Context): unknown;
+
+/**
+ * Import will remove at compile time
  */
-export declare const defaultConfiguration: ConfigurationInterface;
 /**
  * Merges user configurations with CLI configurations and default settings
  * to produce a final configuration object for the build process.
@@ -2904,7 +3124,7 @@ export declare const defaultConfiguration: ConfigurationInterface;
  * console.log('Merged Configuration:', finalConfigs);
  * ```
  */
-export declare function configuration(userConfig: Array<PartialDeepConfigurationsType> | PartialDeepConfigurationsType, cliConfig?: PartialDeepConfigurationsType): Promise<Array<ConfigurationInterface>>;
+declare function configuration(userConfig: Array<PartialDeepConfigurationsType> | PartialDeepConfigurationsType, cliConfig?: PartialDeepConfigurationsType): Promise<Array<ConfigurationInterface>>;
 /**
  * Merges CLI arguments with a configuration file to produce a final configuration object.
  * This function reads the specified configuration file and merges its contents with
@@ -2932,55 +3152,24 @@ export declare function configuration(userConfig: Array<PartialDeepConfiguration
  * });
  * ```
  */
-export declare function cliConfiguration(configFile: string, cli: Argv<ArgvInterface>): Promise<Array<ConfigurationInterface>>;
+declare function cliConfiguration(configFile: string, cli: Argv<ArgvInterface>): Promise<Array<ConfigurationInterface>>;
+
 /**
- * Main run function that initiates the build process based on CLI arguments.
- *
- * This function parses the CLI arguments, configures the build settings, and executes
- * the appropriate build tasks, including type checking, serving, or running in debug mode.
- *
- * @param argv - An array of strings representing the CLI arguments.
- *
- * @returns A promise that resolves when all build tasks are completed.
- *
- * @example
- * ```ts
- * await buildWithArgv(process.argv);
- * ```
+ * Import will remove at compile time
  */
-export declare function buildWithArgv(argv: Array<string>): Promise<void>;
 /**
- * Builds the project using a configuration file specified by its path.
- *
- * This function reads the configuration from the provided file path, processes it,
- * and initiates the build tasks.
- *
- * @param configFilePath - The path to the configuration file to be used for the build.
- *
- * @returns A promise that resolves to an array of `BuildResult` objects once all build tasks are completed.
- *
- * @throws Error Throws an error if the configuration file does not exist or is invalid.
+ * The default configuration options for the build.
  *
  * @example
  * ```ts
- * const results = await buildWithPath('./config.ts');
- * console.log('Build results:', results);
- * ```
- */
-export declare function buildWithConfigPath(configFilePath: string): Promise<BuildResult[]>;
-/**
- * Builds the project based on the provided configuration object.
- *
- * This function processes the given configuration and executes the build tasks accordingly.
+ * import { defaultConfiguration } from '@configuration/default-configuration';
  *
- * @param config - A partial configuration object used to define the build settings.
+ * console.log(defaultConfiguration);
+ * ```
  *
- * @returns A promise that resolves to an array of `BuildResult` objects once all build tasks are completed.
+ * In this example, the `defaultConfiguration` is imported and logged to the console to view the default settings.
  *
- * @example
- * ```ts
- * const results = await build({ entryPoints: ['./src/index.ts'] });
- * console.log('Build results:', results);
- * ```
+ * @public
+ * @category Configuration
  */
-export declare function build(config: PartialDeepConfigurationsType): Promise<BuildResult[]>;
+declare const defaultConfiguration: ConfigurationInterface;