Silent Mode
Control logging and output verbosity
Silent Mode
Packem has no silent config option and no --silent CLI flag. Logging verbosity is controlled by the debug option / --debug behaviour and the environment flags described below.
Build output verbosity in Packem is driven by a debug/verbose toggle rather than a "silent" switch. The only verbosity-related control that exists in the config is debug.
debug
The debug option enables verbose logging. It is part of BuildOptions:
import { defineConfig } from '@visulima/packem/config'
export default defineConfig({
debug: true,
})When enabled, Packem emits additional logger.debug(...) output (for example, where the config file was found) and passes debug through to jiti, which loads your config and entry files.
Environment flags
The --production and --development CLI flags (mutually exclusive) set the build environment, which in turn affects defaults such as minification. They do not silence logging, but they are the primary way to switch a build's mode from the command line:
packem build --production
packem build --developmentWhat does not exist
For accuracy, note the following are not available:
- No
silent: trueconfig key. - No
--silentor--quietCLI flag. - No
logLevel/verbosityconfig option.
If you need quieter output, the practical lever is to leave debug off (its default), which suppresses the verbose debug stream.
Related Options
- Platform -
environmentand the--production/--developmentflags - Watch Mode - Development workflow logging