api #

These extend the CLI args for tasks. Anything can be assigned to a task's args. It's just a mutable POJO dictionary. Downstream tasks will see args that upstream events mutate, unless invoke_task is called with modified args. Upstream tasks can use listeners to respond to downstream events and values. It's a beautiful mutable spaghetti mess. cant get enough The raw CLI args are handled by mri - https://github.com/lukeed/mri

This file is created dynamically by render_sveltekit_shim_app_environment but exists here for the sake of the Node loader. There may be a cleaner workaround but I couldn't find it.

Metadata stored in .gro/ directory to track build cache validity. Schema validates structure at load time to catch corrupted cache files.

Metadata about a single build output file. Includes cryptographic hash for validation plus filesystem stats for debugging and optimization.

Collects information about all files in build output directories. Returns an array of entries with path, hash, size, mtime, ctime, and mode.

Files are hashed in parallel for performance. For very large builds (10k+ files), this may take several seconds but ensures complete cache validation.

Computes the cache key components for a build. This determines whether a cached build can be reused.

Configures process output handling with path replacements while preserving ANSI colors.

Transforms a RawGroConfig to the more strict GroConfig. This allows users to provide a more relaxed config. Hashes the build_cache_config and deletes the raw value for security.

Creates build cache metadata after a successful build. Automatically discovers all build output directories (build/, dist/, dist_*).

The parsed SvelteKit config for the cwd, cached globally at the module level.

Discovers all build output directories in the current working directory. Returns an array of directory names that exist: build/, dist/, dist_*

SHA-256 hash of empty string, used for configs without build_cache_config. This ensures consistent cache behavior when no custom config is provided.

Adds support for imports to both .ts and .js, as well as imports without extensions that resolve to .js or .ts. Prefers .ts over any .js, and falls back to .ts if no file is found.

Searches the filesystem for the CLI name, first local to the cwd and then globally.

Finds modules from input paths. (see src/lib/input_path.ts for more)

Finds modules from input paths. (see src/lib/input_path.ts for more)

Formats a directory on the filesystem. If the source directory is given, it also formats all of the root directory files. This is separated from ./format_file to avoid importing all of the prettier code inside modules that import this one. (which has a nontrivial cost)

Formats a file with Prettier.

Gets a list of possible source ids for each input path with extensions, duplicating each under root_dirs, without checking the filesystem.

Length of git commit hash when displayed in logs (standard git convention).

Paths for the Gro package being used by the user repo.

The config that users can extend via gro.config.ts. This is exposed to users in places like tasks and genfiles.

Invokes Gro tasks by name using the filesystem as the source.

When a task is invoked, Gro first searches for tasks in the current working directory. and falls back to searching Gro's directory, if the two are different. See src/lib/input_path.ts for info about what "task_name" can refer to. If it matches a directory, all of the tasks within it are logged, both in the current working directory and Gro.

This code is particularly hairy because we're accepting a wide range of user input and trying to do the right thing. Precise error messages are especially difficult and there are some subtle differences in the complex logical branches. The comments describe each condition.

Main function to check if the build cache is valid. Returns true if the cached build can be used, false if a fresh build is needed.

Loads build cache metadata from .gro/ directory. Invalid or corrupted cache files are automatically deleted.

Loads a single env value without merging it into process.env. By default searches process.env, then a local .env if one exists, then ../.env if it exists. Empty strings are semantically the same as undefined for more ergonomic fallbacks.

Loads a SvelteKit config at dir.