npm quick
🚀 Versión 1.3.1 — 7 de julio de 2026
¡Soporte para Bun, Deno, colores ANSI de terminal, mejoras de foco de ejecución y caja de resumen de auditoría!
- Detección de Bun y Deno mediante ficheros de configuración (
deno.json, deno.jsonc) y lockfiles.
- Soporte para campos
"packageManager" y "engines" en package.json.
- Visualización de colores ANSI de terminal e interactividad con auto-foco en la entrada.
- Enfoque visual automático de la ejecución en la Tree View y optimizaciones para eliminar parpadeos de panel.
- Caja de resumen de vulnerabilidades tras la finalización del comando
audit (npm, pnpm, yarn, bun).
- Consulta el CHANGELOG para ver todos los detalles.
A lightweight VS Code extension that makes it easy to discover and run npm/pnpm/yarn/bun/deno scripts directly from the Command Palette.
Get it from VS Code Marketplace
Features
✨ Quick Script Discovery - Browse all scripts defined in your config via Command Palette or keyboard shortcut
🚀 Automatic Package Manager Detection - Automatically detects whether your project uses npm, pnpm, yarn, bun, or deno based on lock files, config files, packageManager, and engines configuration fields.
📊 Interactive Output Panel - Dedicated execution panel with terminal ANSI colors, real-time output, input support, and process control
⏹️ Process Control - Stop running scripts gracefully with Ctrl+C or delete execution history entries
📜 Execution History - Track all executed scripts with status indicators (running, completed, failed) and view previous output logs
🔄 Multiple Processes Support - Run multiple scripts simultaneously and switch between their outputs without losing logs
🌍 Multilingual Support - Full internationalization support for Spanish, English, French, German, Portuguese, and Italian
💻 No Configuration Required - Works out of the box with any project that has scripts in package.json
⌨️ Keyboard Shortcuts - Quick access with Cmd+Alt+N (macOS) or Ctrl+Alt+N (Windows/Linux), or Ctrl+. to open the panel
🎯 Status Bar Integration - Quick access icon (📦) in the bottom status bar for one-click panel access
Requirements
- VS Code 1.107.0 or higher (including Antigravity)
- A
package.json file with a scripts section in your project
Quick Start
- Install from VS Code Marketplace
- Open a project folder that contains a
package.json with scripts
- Choose your preferred access method:
- Option A (Status Bar Icon - Quickest): Click the 📦 icon in the bottom status bar
- Option B (Keyboard Shortcut): Press
Ctrl+. to open the panel, or Cmd+Alt+N (macOS) / Ctrl+Alt+N (Windows/Linux) to run a script
- Option C (Command Palette): Press
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux), type "npm quick"
- Select the script you want to run from the Scripts view or use the Command Palette
- The script executes in the NPM QUICK output panel with real-time updates
Usage Examples
Running a Script
- Press
Cmd+Alt+N (macOS) or Ctrl+Alt+N (Windows/Linux)
- Select the script you want to run
- Output appears in the NPM QUICK panel with real-time updates
Stopping a Running Script
- While a script is running, the ⏹️ Stop button appears in the NPM QUICK panel
- Click the Stop button to terminate the process with Ctrl+C
Viewing Script History
- All executed scripts appear in the Scripts view with status indicators:
- 🔵 Running: Script is currently executing
- ✅ Completed: Script finished successfully (exit code 0)
- ❌ Failed: Script failed (non-zero exit code)
- Click any script to view its output logs
- Click the 🗑️ Delete button to remove entries from history
Running Multiple Scripts Simultaneously
- Execute multiple scripts at the same time (e.g., dev server + build watcher)
- All running scripts appear in the Scripts view with 🔵 indicators
- Click on any script to view its real-time output logs
- Each script maintains its own output history and can be controlled independently
- Stop individual scripts using the ⏹️ Stop button when viewing their output
- Send input to specific scripts when they require interactive input
Interactive Scripts
- Scripts that require input (e.g., prompts) show an input field in the NPM QUICK panel
- Type and press Enter to send input to the running script
Clearing History
- In the Scripts view, click the clear icon in the toolbar
- Confirm the action to remove all execution history
How It Works
The extension:
- Reads your project's configuration file (
package.json, deno.json, or deno.jsonc)
- Extracts all scripts or tasks defined inside
- Displays them in a searchable quick pick interface
- Detects your package manager or engine based on lock files, config files,
"packageManager", or "engines" fields:
pnpm-lock.yaml → uses pnpm run <script>yarn.lock → uses yarn <script>bun.lockb / bun.lock → uses bun run <script>deno.lock / deno.json / deno.jsonc → uses deno task <script>package-lock.json / npm-shrinkwrap.json → uses npm run <script>- No lock file/config → defaults to
npm run <script>
- Executes the selected script in a dedicated NPM QUICK output panel
- Tracks execution status and stores output in history
- Allows interactive control (stop, clear history, view logs)
- Displays UI in your configured language
Supported Package Managers
| Package Manager |
Lock File / Config |
Command |
| npm |
package-lock.json, npm-shrinkwrap.json |
npm run <script> |
| pnpm |
pnpm-lock.yaml |
pnpm run <script> |
| yarn |
yarn.lock |
yarn <script> |
| bun |
bun.lockb, bun.lock |
bun run <script> |
| deno |
deno.lock, deno.json, deno.jsonc |
deno task <script> |
Command Reference
npm quick: Run Script
- Command ID:
npm-quick.runScript
- Default Keybinding:
- macOS:
Cmd+Alt+N
- Windows/Linux:
Ctrl+Alt+N
- Alternative: Use Command Palette (
Cmd+Shift+P / Ctrl+Shift+P) and search for "npm quick"
- Description: Displays a quick pick menu with all available scripts from
package.json
npm quick: Open Panel
- Command ID:
npm-quick.openPanel
- Default Keybinding:
Ctrl+. (both macOS and Windows/Linux)
- Status Bar: Click the 📦 icon in the bottom status bar
- Alternative: Use Command Palette and search for "npm quick: Open Panel"
- Description: Opens the NPM QUICK panel showing Scripts view and Output view
Tips & Tricks
- Search Filtering: Start typing in the quick pick to filter scripts by name
- Partial Matches: The quick pick searches both script names and their descriptions
- Switch Between Scripts: Click on different scripts in the history to view their output logs instantly
- Stop Long-Running Scripts: Use the Stop button instead of killing the terminal to gracefully terminate processes
- Language Auto-Detection: The UI automatically displays in your VS Code language preference
Troubleshooting
No scripts appear in the list
- Ensure your project has a valid
package.json, deno.json, or deno.jsonc file
- Check that the
scripts or tasks section exists and contains at least one script
- Make sure VS Code has opened a workspace folder
Wrong package manager is detected
- The extension detects the package manager based on lock files, configuration files (
deno.json), or "packageManager" / "engines" fields in package.json
- Ensure the correct lock file or configuration exists in your project root
- If using npm without
package-lock.json, install dependencies to generate it: npm install
Script doesn't execute
- Check that the script or task syntax is correct in your configuration file
- Verify that required dependencies for the script are installed
- Check the NPM QUICK panel output for error messages
- Ensure the process is actually running (button should be blue when active)
- Some scripts may ignore SIGINT signals - verify the script handles interrupts
- If the script doesn't stop, the process may be blocking signal handling
Output not persisting when switching scripts
- The extension stores output for all executed scripts
- Output is kept in memory during the session
- Restarting VS Code will clear the execution history
Development
This extension is built with TypeScript and uses the VS Code Extension API.
Setup Development Environment
npm install
Compile
npm run compile
Watch Mode
npm run watch
Run Tests
npm run test
Lint Code
npm run lint
Contributing
Contributions are welcome! Please see CONTRIBUTING.md for guidelines on how to contribute, including:
- Bug reports
- Feature requests
- Development setup
- Code style and commit message conventions
- Signed commits requirement - All commits must be signed with a GPG key for security purposes
Known Issues
None at this time.
License
MIT - See LICENSE file for details
Support
If you encounter any issues, please report them on GitHub Issues
Happy scripting! 🚀
