this post was submitted on 07 Sep 2023
4 points (83.3% liked)

VS Code

788 readers
2 users here now

founded 1 year ago
MODERATORS
 

Early last year, I forked a project that had gone idle. I did a couple of updates to make it work with the new version of VSCode, and released it on both marketplaces. It has a few downloads, and no one has yelled at me yet, so I'm not the only one that uses it I guess.

I want to update it with some newer packages out there, updated security versions, and other bits such as the move from vscode-test to @vscode/test-electron, but I'm hitting a block (in not knowing JS/TS very well, most of my 30 years has been with C#, Perl, PHP, SQL, etc.), and I was wondering if anyone had an article or suggestion on documentation how to make that move.

Or am I just starting over with "how to set up test-electron from scratch" and redoing all the tests? :) (that was not my hope for a quick update turn around, but if that is what has to happen...)

edit: a phrase

you are viewing a single comment's thread
view the rest of the comments
[–] Lodra@programming.dev 2 points 1 year ago

Unfortunately, I don't have good info for you. But in my opinion, this is a fine place to ask the question!