Fabr for VS Code

Shows VS Code's TypeScript, and its Java support, a fabr project as fabr builds it. Fabr builds from its build files, not from a node_modules directory or a tsconfig.json, so without this extension the editor finds nothing useful, or a different project of the same name above it.

• Every import resolves to what the build resolves it to: a dependency to the version the build selected, a package the project builds to its source, an import the build would refuse to nothing.
• A package's tests are checked as its test run compiles them, with their test dependencies.
• Go-to-definition, completions and auto-import work across the project's packages, and an unsaved edit in one package shows at once in the packages that import it.
• A TypeScript file's auto-import offers only what its own target can import.
• With Red Hat's Java extension installed, each jar_package is a Java project of the editor's: its sources, the jars the build compiles them against, and its tests with their own test dependencies.
• Fabr's build files (PROJECT.fabr, BUILD.fabr) are highlighted, with an outline, go-to-definition, hover documentation, completion, and their errors in the Problems view.
• Build and Test above each target, the Fabr: Build Target and Fabr: Test Target commands, and the Testing view build and test targets in the fabr the editor already runs, each test's outcome shown beneath its target.

A project that is not fabr's, around or beside a fabr project, keeps VS Code's ordinary behaviour.

Requirements

A workspace holding a PROJECT.fabr, trusted, and fabr installed: in the project's node_modules, on the PATH, or named by the fabr.command setting. The extension runs that fabr's fabr build-server to describe the project.

Settings

• fabr.command: the command running the project's fabr, as a list of arguments; a leading ./ is the workspace folder. A lone .js file, such as an installation's node_modules/@fabr-build/cli/bin/fabr.js, runs on VS Code's own Node.js, so starting it needs nothing from the PATH. Empty (the default): the fabr installed in the project's node_modules, run the same way, else fabr on the PATH.

To start VS Code's TypeScript server through fabr's wrapper, the extension sets the user settings js/ts.tsdk.path and typescript.tsdk to ~/.fabr/vscode/tsdk, which runs VS Code's own TypeScript, once a fabr project has TypeScript or JavaScript targets. The wrapper changes nothing in a window with no fabr project open. Remove the two settings to undo it.

Limitations

• The editor's TypeScript is VS Code's own, not the version the build compiles with; where the two differ, the editor may report an error the build does not, or miss one.
• TypeScript, JavaScript, Java and fabr's build files only: stylesheets are left to VS Code's own support.

See VS Code support in fabr's documentation.