Flow Launcher Node.js Plugins: Setup and Error Checks
JavaScript and TypeScript plugins can use Node.js to communicate with Flow Launcher through JSON-RPC. Their runtime and dependency requirements come from the plugin author. A Node version shown in an old build-workflow example is not automatically the right runtime for every current plugin.
Steps to follow
- Read the plugin’s release instructions and identify its expected Node.js version and entry file.
- Check the Node executable path used by Flow. Confirm it exists after moving or updating a portable setup.
- Use the distributed plugin package, including its bundled dependencies. Run development dependency commands only when you are actually building the source.
- Test a minimal query and inspect the specific runtime error. Compare a plugin failure with a working built-in plugin before changing the launcher.
Check the result
The plugin can start its process and return a result through Flow. A JavaScript syntax error should be reported to the relevant plugin with its version.
Limits and common pitfalls
Do not globally replace Node.js for all applications to satisfy one unexplained plugin error. Check the plugin’s supported configuration first.
Make the check repeatable
The project’s Node.js examples describe packaging node_modules with a plugin release. Old example workflow versions should not be copied as current recommendations. The important diagnostic distinction is whether Flow cannot find Node, Node cannot load the entry file, or the plugin fails after starting.
Questions and answers
Does installing a JavaScript plugin mean I need a development environment?
Not necessarily. A packaged release may include dependencies; follow its user-facing setup instructions rather than its contributor build steps.
Sources and scope
Related guides
Move from Wox to Flow Launcher: Rebuild and Verify
Moving from Wox to Flow Launcher is best treated as a configuration migration rather than a blind folder copy. Record the workflows you use, install Flow.
Flow Launcher vs PowerToys Run: Compare Your Workflow
Flow Launcher and PowerToys Run both provide keyboard-driven launching on Windows. Compare the plugins, search behavior, settings, and maintenance model.
Flow Launcher vs Everything: Different Roles, Shared Search
Flow Launcher is a multi-purpose keyboard launcher, while Everything specializes in file searching. They are not necessarily alternatives: Flow’s Explorer.