The Oxidation Compiler is creating a suite of high-performance tools for JavaScript and TypeScript.
A high-performance JavaScript/TypeScript linter.
- Inline diagnostics with highlighting for warnings and errors.
- Quick fixes to resolve issues when available.
- Command to apply all auto-fixable issues in the current editor.
- Automatically apply fixes on save.
- Configurable run trigger: lint on type or on save.
- Type-aware rules support for enhanced linting.
- Custom icons for Oxlint configuration files.
- JSON schema validation for
.oxlintrc.jsonconfiguration files. - Configurable file extensions (.js, .jsx, .ts, .tsx, .cjs, .mjs, .cts, .mts, .vue, .svelte, .astro).
A high-performance JavaScript/TypeScript formatter.
- Format code via right-click context menu.
- Format code with the built-in actions and their shortcuts (Code > Reformat Code, Code > Reformat File...)
- Automatically format on save.
- JSON schema validation for
.oxfmtrc.jsonconfiguration files. - Configurable file formats JavaScript, TypeScript, JSON, HMYL, Markdown, MDX, CSS, SCSS, GrapghQL, TOML, YAML and more. See the full list.
-
Using the IDE built-in plugin system:
Settings/Preferences > Plugins > Marketplace > Search for "Oxc" > Install
-
Manually:
Download the latest release and install it manually using Settings/Preferences > Plugins > ⚙️ > Install plugin from disk...
IntelliJ provides log files for standard logs as well as the LSP integration. The plugin uses the regular log
directories which can be found
here https://www.jetbrains.com/help/idea/directories-used-by-the-ide-to-store-settings-caches-plugins-and-logs.html#logs-directory.
All LSP logs are output to language-services/Oxfmt* or language-services/Oxlint*. Non-LSP logs are output to
idea.log.
The log level can be configured with the information available
here https://youtrack.jetbrains.com/articles/SUPPORT-A-43/How-to-enable-debug-logging-in-IntelliJ-IDEA.
com.github.oxc.project.oxcintellijplugin:all - Enable debug logging for the plugin.
com.intellij.platform.lsp:all - Enable debug logging for LSP integrations.
Enabling both debug logging for the plugin and debug logging for LSP integrations will typically provide useful information for investigating problems.