export declare const hasDebugFlag: (args?: string[]) => boolean;
export declare const hasSerialFlag: (args?: string[], env?: NodeJS.ProcessEnv) => boolean;
/**
 * Parse process arguments.
 *
 * This function mutates the input list by removing the command name element.
 * Downstream commands can access their args with an ordinary
 * `process.argv.slice(2)`.
 *
 * Example input:
 *
 * ```typescript
 * ['/bin/node', 'node_modules/.bin/skuba', 'test', '--foo', '--bar']
 * ```
 */
export declare const parseProcessArgs: (args?: string[]) => {
    commandName: string;
    args: string[];
};
interface RunArgs {
    /** The conditions to pass to the entry point script. */
    conditions?: string[];
    /** The path to the entry point script. */
    entryPoint?: string;
    /** The port to start an HTTP server on. */
    port?: number;
    /** Arguments passed through to the Node.js executable. */
    node: string[];
    /** Arguments passed through to the entry point script. */
    script: string[];
}
/**
 * Make a best effort to parse "run" args.
 *
 * These are arguments that would be passed to `skuba node` or `skuba start`.
 * Parsing is handrolled because we support some weird and wonderful behaviour:
 *
 * - The `--port` option may be intended for skuba itself
 * - The `--inspect` options may be intended for the Node.js inspector
 * - The entry point may be omitted in favour of `package.json` inference
 * - Other args may be intended for propagation to the entry point
 */
export declare const parseRunArgs: (argv: string[]) => RunArgs;
export {};