https://github.com/codeverdotdev/codever-vscode
Easy save and search snippets to Codever from Visual Studio Code
https://github.com/codeverdotdev/codever-vscode
snippet-manager snippets vscode vscode-extension
Last synced: 9 months ago
JSON representation
Easy save and search snippets to Codever from Visual Studio Code
- Host: GitHub
- URL: https://github.com/codeverdotdev/codever-vscode
- Owner: CodeverDotDev
- License: other
- Created: 2021-04-08T04:47:51.000Z (almost 5 years ago)
- Default Branch: main
- Last Pushed: 2023-05-02T14:32:27.000Z (over 2 years ago)
- Last Synced: 2025-04-03T07:11:18.654Z (10 months ago)
- Topics: snippet-manager, snippets, vscode, vscode-extension
- Language: TypeScript
- Homepage: https://marketplace.visualstudio.com/items?itemName=codever.vscode-codever
- Size: 3.29 MB
- Stars: 4
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Codever Visual Studio Code Extension
Save and search snippets to [Codever](https://www.codever.dev) from Visual Studio Code. You need to have a
[registered account](https://www.codever.dev/register) first.
> [Extensions](https://www.codever.dev/howto) are available also for browsers and IntelliJ IDEs. See our [howto](https://www.codever.dev/howto) guides
> to help you get started.
## Features
### Save snippets
Select snippet, then **right click** or **Ctrl+Shift+P** (**Cmd+Shift+P** on Mac) and select "Save snippet to Codever":

### Search my snippets
**Right click** or **Ctrl+Shift+P** (**Cmd+Shift+P** on Mac) and select "Search my snippets on Codever":

## Publish
Use [`vsce`](https://vscode-docs.readthedocs.io/en/latest/tools/vscecli/) to package
and [publish](https://code.visualstudio.com/api/working-with-extensions/publishing-extension) the extension:
```shell
vsce package
```
```shell
vsce publish
```
> Publisher is `codever` configured in [package.json](package.json) and the managing organisation is
> **CodeverDotDev**
> One needs to be logged in before publishing `vsce login` where a personal access token is passed
> to the vsce cli