-
Hi, But I run into a problem when I try to package the extension into a .vsix file. To generate the file I first run
This will generate the .vsix file with around 15MB which looks fine on the first glance. I can install the .vsix file within VS-Code successfully. But the problem is, that the extension can not be activated within VS-Code as the activation failed because of a missing module:
And inspecting the .vsix file shows that the I played around some time to fix this issue by myself. But so far I did not found a solution. The problem can actually reproduced with the glsp-vscode-intgegration example. Does anybody here has already created a VS-Code .vsix extension file form a GLSP Diagram? Thanks for any hints... |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
It looks like I somehow made it. Compared to the workflow example, I mainly made changes to the package.json file in the /extension/ directory. The interesting part looks now like this: "dependencies": {
"@vscode/codicons": "^0.0.25",
"reflect-metadata": "^0.1.13",
"sprotty-vscode-protocol": "0.3.0",
"@eclipse-glsp/vscode-integration": "1.1.0-RC04"
},
"main": "./lib/index",
"devDependencies": {
"@types/vscode": "^1.54.0",
"path": "^0.12.7",
"ts-loader": "^6.2.1",
"ts-node": "^10.8.2",
"@typescript-eslint/eslint-plugin": "^5.20.0",
"@typescript-eslint/parser": "^5.20.0"
},
"resolutions": {
"**/sprotty": "0.13.0-next.f4445dd.342"
},
"workspaces": {
"packages": [
"**/@vscode/codicons",
"**/@vscode/codicons/**",
"**/open-bpmn-vscode-webview"
]
} In the
This is necessary for the activation of the extension. I also added the
(I do still not understand this part) And in the
(the @vscode/codeicons are irritating and should not be needed) And finally in the
To build the extension .vsix file I run:
Now the .vsix file can be installed and is activated correctly. |
Beta Was this translation helpful? Give feedback.
It looks like I somehow made it.
Compared to the workflow example, I mainly made changes to the package.json file in the /extension/ directory. The interesting part looks now like this: