is there any extension for webstorm?

[inside5545]

is there any extension for webstorm?

[IWANABETHATGUY]

If you are using the paid JetBrain products, the integration should be pretty simple, https://blog.jetbrains.com/platform/2023/07/lsp-for-plugin-developers/

[bc-m]

Maybe it is worth taking a look at Biomes IntelliJ plugin.

[IWANABETHATGUY]

I am already working on the intellij plugin

[IWANABETHATGUY]

A MVP version has been finished, https://github.com/IWANABETHATGUY/oxc-intellij-plugin/tree/main,
I will publish it to market ASAP

[Boshen]

A MVP version has been finished, https://github.com/IWANABETHATGUY/oxc-intellij-plugin/tree/main, I will publish it to market ASAP

Can you move it to the oxc-project org?

[IWANABETHATGUY]

A MVP version has been finished, https://github.com/IWANABETHATGUY/oxc-intellij-plugin/tree/main, I will publish it to market ASAP

Can you move it to the oxc-project org?

I would move to oxc-project after I clean up the code.

[winjeysong]

A MVP version has been finished, https://github.com/IWANABETHATGUY/oxc-intellij-plugin/tree/main, I will publish it to market ASAP

Can you move it to the oxc-project org?

I would move to oxc-project after I clean up the code.

Thanks for your working!
When will the plugin release. I'm really looking forward to that! 😊

[bc-m]

Would love to use oxc in our projects, but we use webstorm instead of vscode. Losing inline lints feels like a downgrade yet. Is this issue open for help or are there any blockers?

If I can help you with testing feel free to ping me. Thank you for your work!

[adoin]

It seems no plugin release for now?

[Smrtnyk]

Any progress on this?
I am really looking forward to oxc but lack of plugin for webstorm is pretty huge blocker

[Smrtnyk]

I have built the extension from the source
I had an issue that I was using node via nvm on ubuntu and didn't have a node alias for #!/usr/bin/env node
but after adding alias oxc plugin wasn't crashing anymore.
Oxc language server was now running and plugin was connected to it.

But the issue I am having now is that my config file oxlint.json that I have in the root of my project is not being picked up.
Doesn't matter which rule I set in the config I see no errors in the IDe, it works when running lint with cli command, but intellij plugin is not flagging errors in the file, I don't see errors in my IDE.
Also seems like this plugin is not running on vue files, altough when linting via cli it works perfectly fine.

[nrayburn-tech]

I don’t have the code open, but I do believe both of your issues are expected. The code hasn’t been setup for that.

For config files, I was waiting for some additional config changes in Oxlint before adding anything to the plugin. Currently I think it only picks up a single config file name, I don’t know what it is though.
I don’t think anything has changed here, still waiting on some Oxlint config enhancements before doing much in the plugin here. Tracked on the plugin side here oxc-project/oxc-intellij-plugin#84.

For Vue files, I think I only added js,jsx, and the TypeScript equivalent files. So there’s quite a few missing that can be added including Vue.
I think this is just file extensions and should be a pretty easy fix. I’ll try to get to it soon, or somebody can submit a PR for it.

[Smrtnyk]

Yeah I added vue to the list of supported extensions and I can see now that oxc is running on vue files now.
I just don't know where to modify extension to make it pick up my oxlint.json file for the config, I am not that familiar with intellij extensions, especially not with oxc stuff.

[nrayburn-tech]

The default is in the language server currently, which is part of the oxc_language_server crate in this repo. If you use a “.eslintrc” file it should be picked up.

This can be configured from the plugin as well, but it’s not as easy to explain. I believe it would be done by modifying this method to return the correct settings. The format in JSON is something like
{“settings”: {“configPath”: “your/path/oxlint.json”}}

[Smrtnyk]

tnx a lot for the pointers @nrayburn-tech, I really appreciate it
I have managed to make it work by hacking the method you mentioned
by doing something like this

override fun createInitializeParams(): InitializeParams {
        val params = super.createInitializeParams()

        val configPath = findConfigPath()
        if (configPath != null) {
            params.initializationOptions = mapOf(
                "settings" to mapOf(
                    "enable" to true,
                    "run" to "onType",
                    "configPath" to configPath  
                )
            )
            thisLogger().debug("Added initializationOptions with configPath: $configPath")
        } else {
            thisLogger().warn("oxlint.json configuration file not found.")
        }

        return params
    }

findConfigPath() is a helper I added to find the file
I had to specify all 3 params because it seems that rust crate didn't consider the options if I only provided the configPath.
I am able to see lint issues now both in ts and vue files