config-file option requires the path to start with a path delimeter

Author: matortheeternalCreated Aug 14, 2026Updated Aug 14, 2026
Labelsbug

Describe the bug The --config-file argument does not operate in a consistent way relative to what is standard for paths provided as arguments from the CLI. It should allow for either a fully qualified system path or a path relative to the current working directory. The current behavior appends appPath, which defaults to ., resulting in a provided argument of --config-file=neutralino.test.config.json failing, and a provided argument of --config-file=/neutralino.test.config.json succeeding.

To Reproduce Steps to reproduce the behavior:

  1. Execute neu run -- --config-file=<path>, replacing <path> with any local path to a file in the CWD, or a fully qualified system path.

Expected behavior This should work like every other path provided as a CLI argument. The path should be resolved in a standard fashion, without requiring workarounds.

Screenshots/Screen recordings N/A

Specifications

  • OS: linux
  • Neutralinojs version: v6.9.0
  • Neutralinojs client library version: v6.9.0
  • Neutralinojs CLI version: v11.7.2

Additional context N/A

Source: neutralinojs/neutralinojs