mirror of
https://github.com/slint-ui/slint.git
synced 2025-12-23 09:19:32 +00:00
8f03e2cff1
This refactor the LSP to be possible to compile for wasm.
When using wasm we can't use the lsp-server crate because that one use the
stdin/stdout to communicate.
Instead, we need will do the communication in TypeScript using the vscode
language server protocol library, and serialize the types to wasm. Fortunately
that's easy because the lsp-types crate contains all the serialized types.
This also "duplicate" the extension as a web extension that do not use process
to start the LSP, but use a web worker. Some of the extension code could
be refactored to avoid some duplication (like the status bar handling and such).
And add a "browser" entry point in the package.json
Finally, add a browserServerMain.ts entry point for our worker, it will try to load
the wasm code.
Currently this doesn't wirk: the browserServerMain.ts can't load the wasm.
Also todo is to write the code so that the wasm code can send the response and
notifications.
To debug, I type these commands in editor/vscode directory
npm run compile-web
code --extensionDevelopmentKind=web --extensionDevelopmentPath=$PWD ../..
22 lines
602 B
JSON
22 lines
602 B
JSON
{
|
|
"compilerOptions": {
|
|
"module": "commonjs",
|
|
"target": "es2020",
|
|
"outDir": "out",
|
|
"lib": [
|
|
"es2020",
|
|
"WebWorker"
|
|
],
|
|
"sourceMap": true,
|
|
"rootDir": ".",
|
|
"strict": true /* enable all strict type-checking options */
|
|
/* Additional Checks */
|
|
// "noImplicitReturns": true, /* Report error when not all code paths in function return a value. */
|
|
// "noFallthroughCasesInSwitch": true, /* Report errors for fallthrough cases in switch statement. */
|
|
// "noUnusedParameters": true, /* Report errors on unused parameters. */
|
|
},
|
|
"exclude": [
|
|
"node_modules",
|
|
".vscode-test"
|
|
]
|
|
}
|