uvr export -o renv.lock does not create a file

[B-Nilson]

running uvr export -o renv.lock outputs the following, but does not create a file like expected

{
  "R": {
    "Version": "4.6.0",
    "Repositories": [
      {
        "Name": "CRAN",
        "URL": "[https://cloud.r-project.org](vscode-file://vscode-app/c:/Program%20Files/Positron/resources/app/out/vs/code/electron-browser/workbench/workbench.html#)"
      }
    ]
  },
  "Packages": {
    "jsonlite": {
      "Package": "jsonlite",
      "Version": "2.0.0",
      "Source": "Repository",
      "Repository": "CRAN"
    }
  }
}

[nbafrank]

@B-Nilson — quick clarification needed before we close or fix this.

Reproducing on current main of the Rust CLI, all three forms of -o write the file as expected:

$ uvr export -o renv.lock
✓ Exported 1 package(s) to renv.lock

$ uvr export --output renv.lock
✓ Exported 1 package(s) to renv.lock

$ uvr export --output=renv.lock
✓ Exported 1 package(s) to renv.lock

--help confirms -o, --output <OUTPUT> is wired correctly, and the flag has been there since v0.2.0.

Was the failing invocation actually the R companion wrapper (uvr::export(out_file = "renv.lock")) rather than the CLI directly? In your PR #5's R/export.R:

if (out_file != "renv.lock") {
  args <- c(args, "-o", out_file)
}

When out_file == "renv.lock" (the default), the conditional skips -o and the CLI defaults to stdout — no file gets created. That matches the symptom you reported here exactly.

Could you confirm:

1. Did you run uvr export -o renv.lock directly in a shell, or via uvr::export() in R?
2. If directly: paste uvr --version.

If it's the wrapper, this folds into PR #5 as a one-line fix.