@codingame/monaco-editor-wrapper 5.3.1 → 5.4.0-full-workbench.1

package/dist/assets/Angular.ng-template-17.1.0.vsix/README.md

@@ -0,0 +1,69 @@
+# Angular Language Service
+
+![demo](https://github.com/angular/vscode-ng-language-service/raw/main/demo.gif)
+
+## Features
+
+This extension provides a rich editing experience for Angular templates, both inline
+and external templates including:
+
+* Completions lists
+* AOT Diagnostic messages
+* Quick info
+* Go to definition
+
+## Download
+
+Download the extension from [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=Angular.ng-template).
+
+## Configuring compiler options for the Angular Language Service
+
+The Angular Language Service uses the same set of options that are used to compile the application.
+To get the most complete information in the editor, set the `strictTemplates` option in `tsconfig.json`,
+as shown in the following example:
+
+```
+"angularCompilerOptions": {
+  "strictTemplates": true
+}
+```
+
+For more information, see the [Angular compiler options](https://angular.io/guide/angular-compiler-options) guide.
+
+## Versioning
+
+The language service extension relies on the `@angular/language-service` and `typescript` packages
+for its backend. `@angular/language-service` is always bundled with the extension, and is always
+the latest version at the time of the release.
+`typescript` is loaded, in order of priority, from:
+
+1. The path specified by `typescript.tsdk` in project or global settings.
+2. _(Recommended)_ The version of `typescript` bundled with the Angular Language Service extension.
+3. The version of `typescript` present in the current workspace's node_modules.
+
+We suggest **not** specifying `typescript.tsdk` in your VSCode settings
+per method (1) above. If the `typescript` package is loaded by
+methods (1) or (3), there is a potential for a mismatch between
+the API expected by `@angular/language-service` and the API provided by `typescript`. This could
+lead to a failure of the language service extension.
+
+For more information, please see [#594](https://github.com/angular/vscode-ng-language-service/issues/594).
+
+## Installing a particular release build
+
+Download the `.vsix` file for the release that you want to install from the [releases](https://github.com/angular/vscode-ng-language-service/releases) tab.
+
+*Do not open the .vsix file directly*. Instead, in Visual Studio code, go to the extensions tab. Click on the "..." menu in the upper right corner of the extensions tab, select "Install from vsix..." and then select the .vsix file for the release you just downloaded.
+
+The extension can also be installed with the following command:
+
+```
+code --install-extension /path/to/ngls.vsix
+```
+
+## Angular Language Service for Other Editors
+
+- [coc-angular](https://github.com/iamcco/coc-angular) for ([Neo](https://neovim.io))[vim](https://www.vim.org/)
+- [nvim-lspconfig](https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#angularls) for [Neovim](https://neovim.io)
+- [Wild Web Developer](https://github.com/eclipse/wildwebdeveloper) for Eclipse
+- [lsp-mode](https://github.com/emacs-lsp/lsp-mode) for Emacs

package/dist/assets/Dart-Code.dart-code-3.81.20240117.vsix/CHANGELOG.md

@@ -0,0 +1 @@
+Full release notes for all versions can be found at [dartcode.org/releases](https://dartcode.org/releases/).

package/dist/assets/Dart-Code.dart-code-3.81.20240117.vsix/README.md

@@ -0,0 +1,89 @@
+[![Discord Chat](https://img.shields.io/badge/chat-discord-blue.svg)](https://discord.gg/xSTPEqm)
+[![Follow on Twitter](https://img.shields.io/badge/twitter-dartcode-blue.svg)](https://twitter.com/DartCode)
+[![Contribute to Dart Code](https://img.shields.io/badge/help-contribute-551A8B.svg)](https://github.com/Dart-Code/Dart-Code/blob/master/CONTRIBUTING.md)
+
+## Introduction
+
+Dart Code extends [VS Code](https://code.visualstudio.com/) with support for the
+[Dart](https://www.dartlang.org/) programming language, and provides tools for
+effectively editing, refactoring, running, and reloading [Flutter](https://flutter.dev/)
+mobile apps.
+
+
+## Installation
+
+Dart Code can be [installed from the Visual Studio Code Marketplace](https://marketplace.visualstudio.com/items?itemName=Dart-Code.dart-code) or by [searching within VS Code](https://code.visualstudio.com/docs/editor/extension-gallery#_search-for-an-extension).
+
+If you have any issues using Dart Code, please file issues on GitHub at [https://github.com/Dart-Code/Dart-Code/issues/new/choose](https://github.com/Dart-Code/Dart-Code).
+
+
+## Features
+
+- Edit and Debug Flutter mobile apps (launch using `F5` or the `Debug` menu)
+- Edit and Debug Dart command line apps (launch using `F5` or the `Debug` menu)
+- [Automatic hot reloads for Flutter](https://dartcode.org/docs/settings/#dartflutterhotreloadonsave)
+- [Refactorings and Code fixes (lightbulb)](https://dartcode.org/docs/refactorings-and-code-fixes/)
+- [Quickly switch between devices for Flutter](https://dartcode.org/docs/quickly-switching-between-flutter-devices/)
+- [Flutter Doctor command](https://dartcode.org/docs/commands/#flutter-run-flutter-doctor)
+- [Flutter Get Packages command](https://dartcode.org/docs/commands/#flutter-get-packages)
+- [Flutter Upgrade Packages command](https://dartcode.org/docs/commands/#flutter-upgrade-packages)
+- [Automatically gets packages when `pubspec.yaml` is saved](https://dartcode.org/docs/settings/#dartrunpubgetonpubspecchanges)
+- [Automatically finds SDKs from `PATH`](https://dartcode.org/docs/configuring-path-and-environment-variables/)
+- [Notification of new stable Dart SDK releases](https://dartcode.org/docs/settings/#dartcheckforsdkupdates)
+- [Sort Members command](https://dartcode.org/docs/commands/#dart-sort-members)
+- Support for debugging "just my code" or SDK/libraries too ([`dart.debugSdkLibraries`](https://dartcode.org/docs/settings/#dartdebugsdklibraries) and [`dart.debugExternalPackageLibraries`](https://dartcode.org/docs/settings/#dartdebugexternalpackagelibraries))
+- [Prompts to get packages when out of date](https://dartcode.org/docs/settings/#dartprompttogetpackages)
+- Syntax highlighting
+- Code completion
+- [Snippets](https://github.com/Dart-Code/Dart-Code/tree/master/snippets)
+- Realtime errors/warnings/TODOs
+- Documentation in hovers/tooltips
+- Go to Definition
+- Find References
+- Rename refactoring
+- Format document
+- Support for format-on-save (`editor.formatOnSave`)
+- Support for format-on-type (`editor.formatOnType`)
+- Workspace symbol search
+- Document symbol search
+- [Organize Imports command](https://dartcode.org/docs/commands/#dart-organize-imports)
+- [Pub Get Packages command](https://dartcode.org/docs/commands/#pub-get-packages)
+- [Pub Upgrade Packages command](https://dartcode.org/docs/commands/#pub-upgrade-packages)
+- [Type Hierarchy](https://dartcode.org/docs/commands/#dart-show-type-hierarchy)
+
+
+## Extension Settings
+
+A full list of settings is [available here](https://dartcode.org/docs/settings/).
+
+
+## Frequently Asked Questions
+
+A list of frequently asked questions is [available here](https://dartcode.org/faq/).
+
+
+## Key Bindings
+
+A list of useful key bindings is [available here](https://dartcode.org/docs/key-bindings/).
+
+
+## Refactorings and Code Fixes
+
+A full list of supported refactors is [available here](https://dartcode.org/docs/refactorings-and-code-fixes/).
+
+
+## Analytics
+
+This extension reports some analytics such as:
+
+- Extension load and analysis times
+- Version numbers for the Dart/Flutter extensions and SDKs
+- The values of some settings (such as Flutter UI Guidelines and Format-on-Save)
+- Frequency of use of features like Hot Reload and Hot Restart
+
+Reporting can be disabled via VS Code's standard **Telemetry: Telemetry Level** setting.
+
+
+## Release Notes
+
+For full release notes, see [the changelog](https://dartcode.org/releases/).

package/dist/assets/IMCTradingBV.svlangserver-0.4.1.vsix/CHANGELOG.md

@@ -0,0 +1,56 @@
+# Changelog
+All notable changes to this repository are documented below.
+
+## [0.4.1] = 2022.05.30
+- Support for Neovim client with nvim-lspconfig
+- Updated settings for faster indexing
+  * Updated libraryIndexing setting to empty by default
+  * Added mustIncludeIndexing setting to glob for files that must be always linted
+  * Added linterWhitelist setting for whitelisting linter errors
+- Bug fixes
+  * for [issue [#19](https://github.com/imc-trading/svlangserver/issues/19)](https://github.com/imc-trading/svlangserver/issues/19)
+  * Updated documentation for [issue [#21](https://github.com/imc-trading/svlangserver/issues/21)](https://github.com/imc-trading/svlangserver/issues/21)
+  * for package linting
+  * for jump to definition
+  * Fix client directory name for newer VSCode
+  * Misc fixes for linter file generation
+
+## [0.4.0] - 2022.03.30
+- Support for Icarus as linting alternative
+- Added command for reporting hierarchy
+- Improved hover over text formatting
+- Support symbol resolution in functions and tasks
+- Bug fixes
+  * for [issue [#19](https://github.com/imc-trading/svlangserver/issues/19)](https://github.com/imc-trading/svlangserver/issues/19)
+  * Fix verilator crash on linting
+  * Fixed verilator diagnostics column number reporting
+
+## [0.3.5] - 2021.10.24
+- Extended keyword and snippets completion
+- Jump to definition improvements
+  * Fix jump to definition for packages
+  * Support jump to definition for includes
+- Added systemverilog.libraryIndexing property
+- Bug fixes
+  * for [issue [#8](https://github.com/imc-trading/svlangserver/issues/8)](https://github.com/imc-trading/svlangserver/issues/8)
+  * for [issue [#10](https://github.com/imc-trading/svlangserver/issues/10)](https://github.com/imc-trading/svlangserver/issues/10)
+  * Typo fix in verilator.ts that caused some editors to hang on exit
+
+## [0.3.4] - 2021.05.31
+- Bug fix for [issue [#1](https://github.com/imc-trading/svlangserver/issues/1)](https://github.com/imc-trading/svlangserver/issues/1)
+- Refectored code to prevent server crashing because of errors
+- Fix verilator linting for systemverilog packages
+
+## [0.3.3] - 2021.05.13
+- Updates for publishing to npm
+- Updates for publishing to vscode marketplace
+- Update installation instructions to use published packages
+
+## [0.3.1] - 2021.04.25
+- Support for Sublime Text 3
+- Support for Emacs
+- Configurable enabling/disabling of language server features viz. Completion, Hover, SignatureHelp
+- Misc bug fixes
+
+## [0.3.0] - 2021.04.22
+- Initial release

package/dist/assets/IMCTradingBV.svlangserver-0.4.1.vsix/README.md

@@ -0,0 +1,320 @@
+# SVLangserver
+A language server for systemverilog that has been tested to work with coc.nvim, VSCode, Sublime Text 4 and emacs
+
+## Features
+- Auto completion (no need for ctags or other such mechanisms)
+- Go to symbol in document
+- Go to symbol in workspace folder (indexed modules/interfaces/packages)
+- Go to definition (_works for module/interface/package names and for ports too!_)
+- Hover over help
+- Signature help
+- Fast indexing
+- Verilator/Icarus linting on the fly
+- Report hierarchy of a module
+- Code snippets for many common blocks
+- Code formatting with verible-verilog-format
+- Elaborate syntax highlighting (for VSCode)
+
+## Versions
+The code has been tested to work with below tool versions
+- vim 8.2
+  * coc.nvim 0.0.80-0b5130ea38
+- VSCode 1.52.0
+- Sublime Text Build 4126
+- emacs 29.0.50
+  * lsp-mode lsp-mode-20220328.1429
+- Neovim 0.7.0
+- Verilator 4.110
+- Icarus Verilog Compiler 10.2
+- Verible v0.0-1114-ged89c1b
+
+## Installation
+- For coc.nvim
+  * `npm install -g @imc-trading/svlangserver`
+  * Update .vim/coc-settings.json
+- For VSCode
+  * Install the extension from the marketplace.
+  * Update the settings
+- For Sublime Text 3
+  * Install the systemverilog package in sublime text
+  * `npm install -g @imc-trading/svlangserver`
+  * Update the LSP settings (`Preferences -> Package Settings -> LSP -> settings`) and the sublime-project files
+- For emacs
+  * Install lsp-mode
+  * `npm install -g @imc-trading/svlangserver`
+  * Update .emacs/init.el
+- For neovim
+  * Install [nvim-lspconfig](https://github.com/neovim/nvim-lspconfig)
+  * `npm install -g @imc-trading/svlangserver`
+  * Add following setting in your init.lua
+  ```lua
+  require'lspconfig'.svlangserver.setup{}
+  ```
+  * Update .nvim/lspconfig.json
+
+To get the snippets, git clone this repo and copy the snippets directory wherever applicable
+
+For installing from source (not applicable for VSCode)
+- `git clone https://github.com/imc-trading/svlangserver.git`
+- `cd svlangserver && npm install`
+  * Update the settings with the correct command (e.g. `/git/repo/path/svlangserver/bin/main.js`)
+
+NOTE: This has been tested with npm version 6.14.13 and node version 14.17.1
+
+## Settings
+- `systemverilog.includeIndexing`: _Array_, Globs defining files to be indexed
+- `systemverilog.libraryIndexing`: _Array_, Globs defining library files to be added to linting. It's useful when module name is not equal to filename.
+- `systemverilog.excludeIndexing`: _Array_, Exclude files from indexing based on glob
+- `systemverilog.linter`: _String_, Select linter
+  * Default: _'verilator'_
+- `systemverilog.launchConfiguration`: _String_, Command to run for launching linting
+  * Default: _verilator --sv --lint-only --Wall_
+  * If not in path, replace _verilator_ with the appropriate command
+- `systemverilog.lintOnUnsaved`: _Boolean_, Lint even unsaved files
+  * Default: _true_
+- `systemverilog.defines`: _Array_, Defines for the project. Used by the language server as well as linting
+  * Default: _empty_
+- `systemverilog.formatCommand`: _String_, verible-verilog-format command for code formatting
+  * Default: _verible-verilog-format_
+  * If not in path, replace _verible-verilog-format_ with the appropriate command
+- `systemverilog.disableCompletionProvider`: _Boolean_, Disable auto completion provided by the language server
+  * Default: _false_
+- `systemverilog.disableHoverProvider`: _Boolean_, Disable hover over help provided by the language server
+  * Default: _false_
+- `systemverilog.disableSignatureHelpProvider`: _Boolean_, Disable signature help provided by the language server
+  * Default: _false_
+- `systemverilog.disableLinting`: _Boolean_, Disable linting
+  * Default: _false_
+- Example coc.nvim settings file
+    ```json
+    {
+        "languageserver": {
+            "svlangserver": {
+                "command": "svlangserver",
+                "filetypes": ["systemverilog"],
+                "settings": {
+                    "systemverilog.includeIndexing": ["**/*.{sv,svh}"],
+                    "systemverilog.excludeIndexing": ["test/**/*.sv*"],
+                    "systemverilog.defines" : [],
+                    "systemverilog.launchConfiguration": "/tools/verilator -sv -Wall --lint-only",
+                    "systemverilog.formatCommand": "/tools/verible-verilog-format"
+                }
+            }
+        }
+    }
+    ```
+    For project specific settings this file should be at `<WORKSPACE PATH>/.vim/coc-settings.json`
+- Example coc.nvim settings file (for windows)
+    ```json
+    {
+        "languageserver": {
+            "svlangserver": {
+                "module": "/usr/lib/node_modules/@imc-trading/svlangserver/bin/main.js",
+                "args": ["--node-ipc"],
+                "filetypes": ["systemverilog"],
+                "settings": {
+                    "systemverilog.includeIndexing": ["**/*.{sv,svh}"],
+                    "systemverilog.excludeIndexing": ["test/**/*.sv*"],
+                    "systemverilog.defines" : [],
+                    "systemverilog.launchConfiguration": "/tools/verilator -sv -Wall --lint-only",
+                    "systemverilog.formatCommand": "/tools/verible-verilog-format"
+                }
+            }
+        }
+    }
+    ```
+    For project specific settings this file should be at `<WORKSPACE PATH>\.vim\coc-settings.json`
+- Example vscode settings file
+    ```json
+    {
+        "systemverilog.includeIndexing": ["**/*.{sv,svh}"],
+        "systemverilog.excludeIndexing": ["test/**/*.sv*"],
+        "systemverilog.defines" : [],
+        "systemverilog.launchConfiguration": "/tools/verilator -sv -Wall --lint-only",
+        "systemverilog.formatCommand": "/tools/verible-verilog-format"
+    }
+    ```
+    For project specific settings this file should be at `<WORKSPACE PATH>/.vscode/settings.json`
+- Example Sublime Text 3 settings files
+  * The global LSP settings file: LSP.sublime-settings
+    ```json
+    {
+        "clients": {
+            "svlangserver": {
+                "enabled": true,
+                "command": ["svlangserver"],
+                "languageId": "systemverilog",
+                "scopes": ["source.systemverilog"],
+                "syntaxes": ["Packages/SystemVerilog/SystemVerilog.sublime-syntax"],
+                "settings": {
+                    "systemverilog.disableHoverProvider": true,
+                    "systemverilog.launchConfiguration": "/tools/verilator -sv --lint-only -Wall",
+                    "systemverilog.formatCommand" : "/tools/verible-verilog-format"
+                }
+            }
+        }
+    }
+    ```
+  * The project specific settings go in `<PROJECT>.sublime-project`
+    ```json
+    {
+        "folders":
+        [
+            {
+                "path": "."
+            }
+        ],
+        "settings": {
+            "LSP": {
+                "svlangserver": {
+                    "settings": {
+                        "systemverilog.includeIndexing": [ "**/*.{sv,svh}", ],
+                        "systemverilog.excludeIndexing": ["test/**/*.sv*"],
+                        "systemverilog.defines": [],
+                    }
+                }
+            }
+        }
+    }
+    ```
+- Example settings for emacs
+  * Below content goes in .emacs or init.el
+    ```elisp
+    (require 'lsp-verilog)
+
+    (custom-set-variables
+      '(lsp-clients-svlangserver-launchConfiguration "/tools/verilator -sv --lint-only -Wall")
+      '(lsp-clients-svlangserver-formatCommand "/tools/verible-verilog-format"))
+
+    (add-hook 'verilog-mode-hook #'lsp-deferred)
+    ```
+  * The project specific settings go in .dir-locals.el
+    ```elisp
+    ((verilog-mode (lsp-clients-svlangserver-workspace-additional-dirs . ("/some/lib/path"))
+                   (lsp-clients-svlangserver-includeIndexing . ("src/**/*.{sv,svh}"))
+                   (lsp-clients-svlangserver-excludeIndexing . ("src/test/**/*.{sv,svh}"))))
+    ```
+- Example neovim settings file
+    ```json
+    {
+        "languageserver": {
+            "svlangserver": {
+                "command": "svlangserver",
+                "filetypes": ["systemverilog"],
+                "settings": {
+                    "systemverilog.includeIndexing": ["**/*.{sv,svh}"],
+                    "systemverilog.excludeIndexing": ["test/**/*.sv*"],
+                    "systemverilog.defines" : [],
+                    "systemverilog.launchConfiguration": "/tools/verilator -sv -Wall --lint-only",
+                    "systemverilog.formatCommand": "/tools/verible-verilog-format"
+                }
+            }
+        }
+    }
+    ```
+    For project specific settings this file should be at `<WORKSPACE PATH>/.nvim/lspconfig.json`
+
+## Commands
+* `systemverilog.build_index`: Instructs language server to rerun indexing
+* `systemverilog.report_hierarchy`: Generates hierarchy for the given module
+
+### coc.nvim usage
+  * The commands should be executed using CocRequest function. An example vim command would be:
+  ```vim
+  command! SvBuildIndex call CocRequest("svlangserver", 'workspace/executeCommand', {'command': 'systemverilog.build_index'})
+  command! -range SvReportHierarchy call CocRequest("svlangserver", 'workspace/executeCommand', {'command': 'systemverilog.report_hierarchy', 'arguments': [input('Module/interface: ', <range> == 0 ? "" : expand("<cword>"))]})
+  ```
+  If the above SvReportHierarchy command is called with visual selection, then the module name is pre-filled with the selection. Also depending on the coc.nvim version, the generated rpt.json file might not have the focus and user will have to switch buffer manually.
+
+### VSCode usage
+  * Typing `build index` in the command palette should invoke the build index command.
+  * Typing `get hierarchy` in the command palette should invoke the report hierarchy command. If invoked with an active slection, the module name is pre-filled with the selection.
+
+### Sublime usage
+  * A sublime-commands file needs to be created with the below content
+  ```json
+  [
+    {
+      "caption": "SvLangserver Build Index",
+      "command": "lsp_execute",
+      "args": {
+        "session_name": "svlangserver",
+        "command_name": "systemverilog.build_index",
+        "command_args": []
+      }
+    },
+    {
+      "caption": "Svlangserver Report Hierarchy",
+      "command": "lsp_execute",
+      "args": {
+        "session_name": "svlangserver",
+        "command_name": "systemverilog.report_hierarchy",
+        "command_args": ["${selection}"]
+      }
+    }
+  ]
+  ```
+  This should make the commands available in the command palette. For the report hierarchy command, the module name should be selected before invoking the command.
+
+### Emacs usage
+  * `lsp-clients-svlangserver-build-index` command should rerun the indexing.
+  * `lsp-clients-svlangserver-report-hierarchy` command should do the job. If invoked with an active slection, the module name is pre-filled with the selection.
+
+### Neovim usage
+  * `:SvlangserverBuildIndex` command should rerun the indexing.
+  * `:SvlangserverReportHierarchy` command will generate hierarchy file of the word under the cursor in normal mode.
+
+## Troubleshooting
+- Editor is not able to find language server binary.
+    * Make sure the binary is in the system path as exposed to the editor. If the binary is installed in custom directory, expose that path to your editor
+- Not getting any diagnostics
+    * Make sure the launchConfiguration setting has been properly set to use verilator from the correct installation path
+- Diagnostics show _Cannot find file containing module 'module_name'_
+    * Make sure all submodules can be found by includeIndexing
+    * If the issue still remains, it may due to different naming of module and file, or a file containing multiple modules. Make sure these files can be found by libraryIndexing.
+- Check settings used by the language server
+    * for coc.nvim: Use the command `:CocCommand workspace.showOutput` and then select svlangserver
+    * for vscode: Check the SVLangServer output channel
+    * for sublime: Open the command palette in the tools menu and select `LSP: Toggle Log Panel`
+    * for emacs: Check the `*lsp-log*` buffer
+    * for neovim: Add `vim.lsp.set_log_level("info")` in your init.lua then check ~/.cache/nvim/lsp.log
+
+## Known Issues
+- Language server doesn't understand most verification specific concepts (e.g. classes).
+
+## Future
+Rewrite parser to make it much more robust
+
+## Acknowledgements
+Although most of the code is written from scratch, this [VSCode-SystemVerilog extension](https://github.com/eirikpre/VSCode-SystemVerilog/) was what I started with and developed on.
+
+## Release Notes
+See the [changelog](https://github.com/imc-trading/svlangserver/blob/HEAD/CHANGELOG.md) for more details
+
+### 0.4.1
+- Support for Neovim client with nvim-lspconfig
+- Updated settings for faster indexing
+- Bug fixes
+
+### 0.4.0
+- Icarus as linting alternative
+- Command for reporting hierarchy
+- Improved hover over formatting
+- Improved symbol resolution
+- Bug fixes
+
+### 0.3.5
+- Improvements to auto-completion and jump to definition
+- Bug fixes
+
+### 0.3.4
+- Bug fixes
+
+### 0.3.3
+- Updated instructions to use published packages
+
+### 0.3.1
+- Add support for Sublime LSP and Emacs
+
+### 0.3.0
+- Initial release