Stone.js API
    Preparing search index...

    Interface CreateAppConfig

    Configuration for creating a new Stone.js Application. Used internally by the init command.

    interface CreateAppConfig {
        destDir?: string;
        initGit: boolean;
        linting: string;
        modules: string[];
        overwrite: boolean;
        packageJson?: PackageJson;
        packageManager: string;
        projectName: string;
        srcDir?: string;
        starters?: string[];
        startersRepo: string;
        template: string;
        templateExplicit?: boolean;
        testing: string;
        typing: string;
    }
    Index
    destDir? initGit linting modules overwrite packageJson? packageManager projectName srcDir? starters? startersRepo template templateExplicit? testing typing
    destDir?: string
    initGit: boolean
    linting: string
    modules: string[]
    overwrite: boolean
    packageJson?: PackageJson
    packageManager: string
    projectName: string
    srcDir?: string
    starters?: string[]

    Starter links (git/npm/local) to fetch, e.g. github:owner/repo, @acme/stone-starters, ./my-starter. Also set via --starters link1,link2. Empty = the built-in default link. The CLI stays agnostic: each linked package declares its own starters via stone.starters in its package.json. Installed starter packages are additionally auto-detected (0-config).

    startersRepo: string
    template: string
    templateExplicit?: boolean

    True when the starter was named explicitly with --starter <id>, so an id that matches no entry must fail instead of silently falling back to the first available starter.

    testing: string
    typing: string

    Settings
    Member Visibility

    On This Page
    Properties