The library directory - SvelteKit has no files.lib option, so it's always here. Lives here rather than in ./paths.ts because it's a constant that reads no config.

LIB_PATH
#

constants.ts view source

string import {LIB_PATH} from '@fuzdev/gro/constants.js';

LOCKFILE_FILENAME
#

constants.ts view source

"package-lock.json" import {LOCKFILE_FILENAME} from '@fuzdev/gro/constants.js';

NODE_MODULES_DIRNAME
#

constants.ts view source

"node_modules" import {NODE_MODULES_DIRNAME} from '@fuzdev/gro/constants.js';

PACKAGE_JSON_FILENAME
#

constants.ts view source

"package.json" import {PACKAGE_JSON_FILENAME} from '@fuzdev/gro/constants.js';

PM_CLI_DEFAULT
#

constants.ts view source

"npm" import {PM_CLI_DEFAULT} from '@fuzdev/gro/constants.js';

SERVER_DIST_PATH
#

constants.ts view source

"dist_server" import {SERVER_DIST_PATH} from '@fuzdev/gro/constants.js';

SOURCE_DIR
#

constants.ts view source

string import {SOURCE_DIR} from '@fuzdev/gro/constants.js';

SOURCE_DIRNAME
#

constants.ts view source

"src" import {SOURCE_DIRNAME} from '@fuzdev/gro/constants.js';

SVELTE_CHECK_CLI
#

constants.ts view source

"svelte-check" import {SVELTE_CHECK_CLI} from '@fuzdev/gro/constants.js';

SVELTE_MATCHER
#

constants.ts view source

RegExp import {SVELTE_MATCHER} from '@fuzdev/gro/constants.js';

SVELTE_PACKAGE_CLI
#

constants.ts view source

"svelte-package" import {SVELTE_PACKAGE_CLI} from '@fuzdev/gro/constants.js';

SVELTE_PACKAGE_DEP_NAME
#

constants.ts view source

"@sveltejs/package" import {SVELTE_PACKAGE_DEP_NAME} from '@fuzdev/gro/constants.js';

SVELTE_RUNES_MATCHER
#

constants.ts view source

RegExp import {SVELTE_RUNES_MATCHER} from '@fuzdev/gro/constants.js';

SVELTE_SCRIPT_MATCHER
#

constants.ts view source

RegExp import {SVELTE_SCRIPT_MATCHER} from '@fuzdev/gro/constants.js';

Extracts the script content from Svelte files.

SVELTEKIT_BUILD_DIRNAME
#

constants.ts view source

"build" import {SVELTEKIT_BUILD_DIRNAME} from '@fuzdev/gro/constants.js';

SVELTEKIT_CLI
#

constants.ts view source

"svelte-kit" import {SVELTEKIT_CLI} from '@fuzdev/gro/constants.js';

SVELTEKIT_DEP_NAME
#

constants.ts view source

"@sveltejs/kit" import {SVELTEKIT_DEP_NAME} from '@fuzdev/gro/constants.js';

SVELTEKIT_DEV_DIRNAME
#

constants.ts view source

".svelte-kit" import {SVELTEKIT_DEV_DIRNAME} from '@fuzdev/gro/constants.js';

SVELTEKIT_DIST_DIRNAME
#

constants.ts view source

"dist" import {SVELTEKIT_DIST_DIRNAME} from '@fuzdev/gro/constants.js';

SVELTEKIT_GLOBAL_SPECIFIER
#

constants.ts view source

RegExp import {SVELTEKIT_GLOBAL_SPECIFIER} from '@fuzdev/gro/constants.js';

SVELTEKIT_TSCONFIG_PATH
#

constants.ts view source

string import {SVELTEKIT_TSCONFIG_PATH} from '@fuzdev/gro/constants.js';

The tsconfig SvelteKit generates for projects to extend as $app/tsconfig.

SVELTEKIT_TSCONFIG_SPECIFIER
#

constants.ts view source

"$app/tsconfig" import {SVELTEKIT_TSCONFIG_SPECIFIER} from '@fuzdev/gro/constants.js';

The extends specifier SvelteKit projects use for the tsconfig that svelte-kit sync generates at SVELTEKIT_TSCONFIG_PATH.

SVELTEKIT_VITE_CACHE_PATH
#

constants.ts view source

string import {SVELTEKIT_VITE_CACHE_PATH} from '@fuzdev/gro/constants.js';

TS_MATCHER
#

constants.ts view source

RegExp import {TS_MATCHER} from '@fuzdev/gro/constants.js';

TSCONFIG_FILENAME
#

constants.ts view source

"tsconfig.json" import {TSCONFIG_FILENAME} from '@fuzdev/gro/constants.js';

VITE_CLI
#

constants.ts view source

"vite" import {VITE_CLI} from '@fuzdev/gro/constants.js';

VITE_CONFIG_FILENAMES
#

constants.ts view source

string[] import {VITE_CONFIG_FILENAMES} from '@fuzdev/gro/constants.js';

Every filename Vite picks up as its config, in Vite's own precedence order. Which one wins is Vite's call, so Gro treats them as a set rather than privileging one extension - it detects a Vite config with all of them, and formats all of them.

VITEST_CLI
#

constants.ts view source

"vitest" import {VITEST_CLI} from '@fuzdev/gro/constants.js';

see also