10 Hidden Tricks in MiniakTools Every Developer Should Know
- Quick scaffold generator
- Use the built-in scaffold flag (
–scaffold) with a component name to generate ready-to-edit component, test, and style files in one command.
- Smart config merging
- MiniakTools supports deep config merging via
miniak.config.json. Place environment-specific snippets inminiak.config.{env}.jsonand MiniakTools will merge them automatically when you run with–env.
- Selective task runner
- Pass
–onlywith a comma-separated list (e.g.,–only=lint,build) to run just specific tasks from your pipeline without executing the full suite.
- Interactive prompt mode
- Run
miniak init –interactiveto answer guided questions; it creates a tailored config and suggests plugins based on your answers.
- Hidden performance profiler
- Enable the profiler with
–profileto produce a lightweight timeline (JSON) of task durations; load it into Chrome DevTools for a flamegraph view.
- Alias-aware imports
- MiniakTools resolves path aliases defined in
miniak.config.json— use@components/Buttonin imports and the bundler will map it correctly at build time.
- Local plugin linking
- Use
miniak link-plugin ./path/to/pluginto symlink a local plugin during development; changes to the plugin are picked up without reinstalling.
- Cache-busting build IDs
- Add
–build-idto produce deterministic hashed filenames for assets tied to that ID, useful for staging deployments where you want repeatable URLs.
- Granular watch mode
miniak watch –patterns=“src//*.{js,ts},styles//*.css” –ignore=”/.spec.“watches only specified files and skips tests, reducing rebuild noise.
- Secret management integration
- MiniakTools can read secrets from a local
.miniak-secretsfile or environment vaults whensecretProvideris set in config; secrets are injected at build time, not stored in output artifacts.
If you want, I can expand any trick into a short how-to with example commands and config snippets.
Leave a Reply