You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now attempt to add the toolkit following the Getting Started Guide.
Expected behavior
The Getting Started Guide should
document the toolkit only (not explain how to create a vscode extension from scratch) and
build on / refer to the existing vscode documentation instead.
This minimizes the possibility that both documentations go out of sync.
The toolkit itself should be in sync with the current vscode extension dependencies. Concretely this means supporting esbuild >= 0.17.x but in general this should be a test case.
The text was updated successfully, but these errors were encountered:
The Getting Started Guide cannot be applied with a recent installation of generator-code... various errors appear during the setup of the example.
In particular in relation to:
The instructions in the Getting Started Guide are incompatible with the vscode environment and with the documentation.
The official guides to build a webview extension and to use a bundler are:
https://github.com/microsoft/vscode-webview-ui-toolkit/blob/main/docs/getting-started.md,
https://code.visualstudio.com/api/extension-guides/webview
and
https://code.visualstudio.com/api/working-with-extensions/bundling-extension
As mentioned in #556, the guide is too long and contradicts the instructions in https://code.visualstudio.com/api/extension-guides/webview and in https://code.visualstudio.com/api/working-with-extensions/bundling-extension
As mentioned in #546, the required esbuild version (16.x) is not supported by the vscode extension environment anymore and leads to build errors.
To reproduce
Follow the instructions to create an extension, then build a webview extension and add esbuild.
Now attempt to add the toolkit following the Getting Started Guide.
Expected behavior
The Getting Started Guide should
This minimizes the possibility that both documentations go out of sync.
The toolkit itself should be in sync with the current vscode extension dependencies. Concretely this means supporting esbuild >= 0.17.x but in general this should be a test case.
The text was updated successfully, but these errors were encountered: