https://github.com/dannymcgee/vscode-klipper
Rich language support for Klipper configuration files and Klipper-flavored GCode
https://github.com/dannymcgee/vscode-klipper
Last synced: 26 days ago
JSON representation
Rich language support for Klipper configuration files and Klipper-flavored GCode
- Host: GitHub
- URL: https://github.com/dannymcgee/vscode-klipper
- Owner: dannymcgee
- Created: 2023-01-11T06:12:41.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-11-24T20:33:18.000Z (5 months ago)
- Last Synced: 2025-04-09T23:12:56.968Z (26 days ago)
- Language: TypeScript
- Homepage:
- Size: 91.8 KB
- Stars: 8
- Watchers: 1
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# VS Code Klipper Support
This repo is an [Nx](https://nx.dev)-managed workspace.
Various parts of the extension are managed through individual projects located
under `/packages/`:
- `klipper`: The primary extension project, where the extension's `package.json`
and TypeScript source code are located.
- `klipper-cfg`: The TextMate grammar for Klipper config files.
- `klipper-gcode`: The TextMate grammar for Klipper-flavored GCode.
- `klipper-script`: The TextMate grammar for interpolated Jinja2/Python
expressions embedded within Jinja2 template tags.
The main workspace configuration is at `/nx.json`, while individual project
configurations can be found at `/packages//project.json`.
Most tasks for building, testing, packaging and publishing are handled through
the Nx CLI:
```sh
# Build, package, and locally install the extension
nx build klipper
# Build without local package & install
nx build klipper --package false --install false
# Build a specific grammar
nx build klipper-cfg
# Note: Dependencies are mapped, changes are tracked, and build results are
# cached, so generally you should just run `nx build klipper` instead.
```
More information for specific projects can generally be found under the
project-level README.