gwen: Rebrand documentation to Gwen
Rewrite product prose and local path/command examples across the docs to match the shipped application (gwen CLI, Gwen config paths, Gwen.app, com.yrkaierx.Gwen). Upstream distribution channels, service URLs and package identifiers stay factually intact.
This commit is contained in:
1 parent
fe62a99bf5
commit
74405573c9
209 files changed
+2275
-2274
No files matched your search
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: JavaScript
|
||||
description: "Configure JavaScript language support in Zed, including language servers, formatting, and debugging."
|
||||
description: "Configure JavaScript language support in Gwen, including language servers, formatting, and debugging."
|
||||
---
|
||||
|
||||
# JavaScript
|
||||
|
||||
JavaScript support is available natively in Zed.
|
||||
JavaScript support is available natively in Gwen.
|
||||
|
||||
- Tree-sitter: [tree-sitter/tree-sitter-javascript](https://github.com/tree-sitter/tree-sitter-javascript)
|
||||
- Language Server: [yioneko/vtsls](https://github.com/yioneko/vtsls)
|
||||
@@ -56,18 +56,18 @@ Configure formatting in Settings ({#kb zed::OpenSettings}) under Languages > Jav
|
||||
|
||||
## JSX
|
||||
|
||||
Zed supports JSX syntax highlighting out of the box.
|
||||
Gwen supports JSX syntax highlighting out of the box.
|
||||
|
||||
In JSX strings, the [`tailwindcss-language-server`](./tailwindcss.md) is used to provide autocompletion for Tailwind CSS classes.
|
||||
|
||||
## JSDoc
|
||||
|
||||
Zed supports JSDoc syntax in JavaScript and TypeScript comments that match the JSDoc syntax.
|
||||
Zed uses [tree-sitter/tree-sitter-jsdoc](https://github.com/tree-sitter/tree-sitter-jsdoc) for parsing and highlighting JSDoc.
|
||||
Gwen supports JSDoc syntax in JavaScript and TypeScript comments that match the JSDoc syntax.
|
||||
Gwen uses [tree-sitter/tree-sitter-jsdoc](https://github.com/tree-sitter/tree-sitter-jsdoc) for parsing and highlighting JSDoc.
|
||||
|
||||
## ESLint
|
||||
|
||||
You can configure Zed to format code using `eslint --fix` by running the ESLint code action when formatting.
|
||||
You can configure Gwen to format code using `eslint --fix` by running the ESLint code action when formatting.
|
||||
|
||||
Configure code actions on format in Settings ({#kb zed::OpenSettings}) under Languages > JavaScript, or add to your settings file:
|
||||
|
||||
@@ -231,7 +231,7 @@ To get all the features (autocomplete, linting, etc.) from the [Tailwind CSS lan
|
||||
|
||||
## Debugging
|
||||
|
||||
Zed supports debugging JavaScript code out of the box with `vscode-js-debug`.
|
||||
Gwen supports debugging JavaScript code out of the box with `vscode-js-debug`.
|
||||
The following can be debugged without writing additional configuration:
|
||||
|
||||
- Tasks from `package.json`
|
||||
@@ -243,7 +243,7 @@ Run {#action debugger::Start} ({#kb debugger::Start}) to see a contextual list o
|
||||
|
||||
> **Note:** Node test is automatically detected when `@types/node` is present in `package.json` (requires Node.js 20+).
|
||||
|
||||
As for all languages, configurations from `.vscode/launch.json` are also available for debugging in Zed.
|
||||
As for all languages, configurations from `.vscode/launch.json` are also available for debugging in Gwen.
|
||||
|
||||
If your use-case isn't covered by any of these, you can take full control by adding debug configurations to `.zed/debug.json`. See below for example configurations.
|
||||
|
||||
|
||||
Reference in new issue
Block a user