Extension doesn't work in "remote development" mode

[skevy]

Thanks for the work on this extension!

I followed the instructions for configuration (directly copied what's in the readme) on 0.4.1, and as expected, formatting worked perfectly. However, as I adjusted settings in my oxfmtrc, they don't seem to take effect when formatting in the editor (e.g., semi set to true, printWidth set to 100, etc). Running oxfmt using npm run works fine and respects the settings as expected.

Seeing as others aren't reporting this, one thing I'm suspect of is that I'm using Zed in "remote development" mode against a remote server. Has this extension been tested in that scenario? Perhaps the LSP is not properly finding the oxfmtrc config in the remote environment?

Let me know what details I can provide to debug this further.

[nrayburn-tech]

I definitely haven’t used it myself ( I don’t use Zed regularly, so I don’t even know how to use remote development with Zed).

You can try to specify the path to the config file directly, but that’s the only suggestion I have at the moment. I think it’s ‘fmt.configPath’. https://github.com/oxc-project/oxc/tree/main/crates/oxc_language_server

[Boshen]

I suspect its due to a different cwd when remoting 🤔

[nrayburn-tech]

Could be. I’ll review the debug logging and update the readme with how to enable it. This may require another release before we can get any useful information for troubleshooting.
That would hopefully give us some extra information to identify what’s going on.

I can also look into debugging a remote server and see if I can just find the issue that way without having to wait for a release with more debug logging.

[coreyward]

Not sure if it's related or not, but I can't get 0.4.1 to pick up lsp configuration directives at all. In the LSP Logs > Server Info it always reports * Configuration: {} now. Perhaps that's always been the case, but when the linter isn't reporting the same as when I run oxlint --type-aware.

"lsp": {
    "oxlint": {
      "initialization_options": {
        "options": {
          "run": "onType",
          "configPath": null,
          "tsConfigPath": null,
          "disableNestedConfig": false,
          "unusedDisableDirectives": "warn",
          "typeAware": true,
        },
      },
    },
  },

[Sysix]

@coreyward try "initialization_options": { "settings": {...}} instead of options

[coreyward]

Thanks. With that change the configuration is being picked up, but its still not matching the output from pnpm oxlint --type-aware. For example, I get a typescript-eslint(no-unsafe-type-assertion) when running with --type-aware, but not when running in Zed.

[nrayburn-tech]

@coreyward could you create a new issue? It sounds like your issue is unrelated.

If you can provide a reproduction in your issue it would help us troubleshoot. If you’re unable to provide a reproduction, we will be a bit limited but something else you can try is using VS Code with the Oxc VS Code plugin and checking if that provides the same wrong output, or if it provides output that matches the CLI.