Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Automate VSIX generation + publishing to VS Code + open-VSX for stable releases
See original GitHub issueDescription
Are there any plans on releasing the extension as a .vsix file?
I noticed on the releases page of the repository that the source is released for a given tag but was wondering if it’d be possible to also include the .vsix as part of the release.
There is the odd .visx occasionally released: https://github.com/Dart-Code/Dart-Code/releases/download/v2.8.0-beta.1/dart-code-3.8.0-beta.1.vsix
The reason I ask is to be able to consume the extension in Theia (which supports VS Code extensions), and namely our Dart docker image.
The workaround at the moment is to fork the repository, perform the releases ourselves in .vsix format) and consume those.
Additional Info
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ah, fair enough! I’ve attached the v3.8.1 vsix files to the corresponding release pages. I’ll try to remember to add them for future versions too, but feel free to ping me if I forget. Maybe at some point I can automate this better (I’d like to do this for dev builds anyway to avoid having to build manually for people wanting to try out fixes).
I’ll re-purpose this issue for providing these more reliably. Thanks!