vscode-marky-stats VS vscode-vsce

Compare vscode-marky-stats vs vscode-vsce and see what are their differences.

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
vscode-marky-stats vscode-vsce
1 3
7 748
- 3.5%
2.9 7.4
almost 1 year ago 3 days ago
JavaScript TypeScript
Apache License 2.0 GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

vscode-marky-stats

Posts with mentions or reviews of vscode-marky-stats. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-06-16.
  • Write a VS Code extension in JavaScript, not TypeScript ^
    7 projects | dev.to | 16 Jun 2021
    Like any JavaScript project, you can use any bundler you wish. Bundling can make even an extension with just a few modules load considerably faster. I looked at this with Marky Stats which has 3 short modules, and it improved the loading time. This is optimization, if you are beginner, do not feel obligated to do it. Pace yourself!

vscode-vsce

Posts with mentions or reviews of vscode-vsce. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-04-08.
  • GitHub Action You Need to Publish VS Code Extensions
    4 projects | dev.to | 8 Apr 2022
    Lastly we will package and publish our extension using the Visual Studio Code Extension Manager and a GitHub Action called HaaLeo/publish-vscode-extension. The advantage of having the packaging and publishing step separated is that we can attach the compiled .vsix file as an artifact to the workflow and offer it as download. Make sure to generate a token (named in the workflow as VSC_MKTP_PAT and OPEN_VSX_TOKEN) to allow GitHub to publish your extension.
  • I automated publishing my VSCode Extension
    2 projects | dev.to | 3 Oct 2021
    I'm using VSCE - VSCode Extension Manager package to build and deploy my project to the Marketplace.
  • Write a VS Code extension in JavaScript, not TypeScript ^
    7 projects | dev.to | 16 Jun 2021
    There is a CLI tool called vsce for packaging and publishing extensions. It's easy to use. This will create a vsix package that can be installed as an extension.

What are some alternatives?

When comparing vscode-marky-stats and vscode-vsce you can also consider the following projects:

AutoIt-VSCode - AutoIt Extension for Visual Studio Code

openvsx - An open-source registry for VS Code extensions

vscode-extension-samples - Sample code illustrating the VS Code extension API.

publish-vscode-extension - GitHub action to publish your VS Code Extension to the Open VSX Registry or Visual Studio Marketplace.

vscode-snippets-ranger - View and edit all of your snippets in one purty place! Yee-haw!!

release-action - An action which manages a github release

vscode-marquee - 💡 The missing VS Code homescreen that helps you to stay organized with minimal context switches

vscode-manager - A VSCode extension to create multiple isolated VSCode instances - with their unique settings and extensions.