stackprobe.config.js file in your project root. This allows you to customize which checks run, how failures are handled, and more.
Creating a Config File
Create astackprobe.config.js file in the root of your project:
stackprobe.config.js
Configuration Options
StackProbe uses theStackProbeConfig interface defined below:
ignore
List of check names to skip during the audit.Available checks:
license- License compatibility checkenv- Environment variable validationdeps- Dependency analysisengine- Node.js engine version checkcircular- Circular dependency detection
only
Run ONLY these specific checks. When set, this overrides the
ignore option.Available checks:license- License compatibility checkenv- Environment variable validationdeps- Dependency analysisengine- Node.js engine version checkcircular- Circular dependency detection
failOn
Determines when StackProbe should exit with a non-zero status code in CI environments.
error(default) - Exit with code 1 only on errorswarn- Exit with code 1 on warnings and errors
Full Example
stackprobe.config.js
Running Specific Checks
To run only dependency and environment checks:stackprobe.config.js
Default Configuration
If no config file is present, StackProbe uses these defaults:Config Loading
StackProbe looks forstackprobe.config.js in the current working directory. If the file cannot be loaded or parsed, a warning is shown and default values are used: