profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/joaomoreno/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
João Moreno joaomoreno Microsoft Zurich, Switzerland https://resume.joaomoreno.com VS Code

joaomoreno/deemon 31

Run a process in the background and attach to it

joaomoreno/facilis 8

Send files through HTTP without hassle.

joaomoreno/dotfiles 2

My dotfiles

joaomoreno/easy_rust 2

Rust explained using easy English

joaomoreno/arduino-rgb-lamp 1

Arduino RGB Lamp

joaomoreno/atom-shell-installer-assets 1

Assets to generate Windows installers for Atom Shell apps

joaomoreno/encodings 1

Encoding samples

joaomoreno/adm-zip 0

A Javascript implementation of zip for nodejs. Allows user to create or extract zip files both in memory or to/from disk

joaomoreno/advent-of-code-2017 0

Advent of Code 2017

fork matklad/prusti-dev

A static verifier for Rust, based on the Viper verification infrastructure.

http://prusti.ethz.ch

fork in 7 hours

startedarrow-py/arrow

started time in 15 hours

created repositorymattbierner/beatsy-app-clip-codes

created time in 15 hours

startedjart/cosmopolitan

started time in 16 hours

starteddyedgreen/uncertain

started time in 16 hours

startedoaeproject/Cake

started time in a day

fork mitsuhiko/envdir-plusplus

kinda like envdir, kinda like dotenv, kinda like docker env-file

fork in a day

fork mitsuhiko/s3autoindex

autoindex for private s3 buckets

fork in a day

created repositorymitsuhiko/similar-asserts

Provides assert_eq! like macros with colorized diff output

created time in 2 days

created repositorymatklad/wsmeta

created time in 2 days

startedjoaomoreno/gifcap

started time in 2 days

issue openedmicrosoft/vscode-vsce

preLaunchTask causes infinite loading when trying to debug

Two days ago I created an extension using the command yo code with following options

  • Typescript
  • Git repo
  • Webpack enabled

An extension I created today has the same setup. The only difference was that if pressing Debug webpack finishes building and then VS Code is loading infinitely. I reinstalled VS Code and tried different versions, later I took a look if there are any changes in the files.

In the new launch.json file I noticed one new line : "preLaunchTask": "${defaultBuildTask}". I didn't find it in the old one and by removing it everything works fine and the Development Host starts successfully.

Hopefully it is the right place to post. :)

created time in 2 days

startedhumbug/php-scoper

started time in 2 days

startedjoaomoreno/gifcap

started time in 2 days

startedShelob9/block-content

started time in 3 days

startedryanburgess/engineer-manager

started time in 3 days

startedunpoly/unpoly

started time in 3 days

startedMoOx/pjax

started time in 3 days

startedmachbarmacher/gdpr-dump

started time in 3 days

startedspiotr12/board-game-geek

started time in 3 days

startedmonteslu/bgg

started time in 3 days

startedablanco/boardgamegeek-telegram-bot

started time in 3 days

created repositorymatklad/rust-inline

created time in 3 days

issue commentmicrosoft/vscode-vsce

Should vsce deal with pre-release version identifiers?

Actually, I checked the spec and since the marketplace doesn't support an alphnumeric tag after a hyphen, it does not use Semantic Versioning v1, which specifies:

A pre-release version number MAY be denoted by appending an arbitrary string immediately following the patch version and a dash. The string MUST be comprised of only alphanumerics plus dash [0-9A-Za-z-].

The marketplace seems to have its own versioning schema.

kdvolder

comment created time in 3 days

issue commentmicrosoft/vscode-vsce

Should vsce deal with pre-release version identifiers?

Just to pile on here -- I should have linked our issue when we hit this.

In particular, in https://github.com/PowerShell/vscode-powershell/issues/1880#issue-433375920 we discuss the fact that npm uses semver v2 whereas the marketplace uses semver v1, meaning extensions are forced to use the intersection of the two; the marketplace doesn't tolerate a prerelease tag, but npm doesn't tolerate a patch version.

kdvolder

comment created time in 3 days

startedjoaomoreno/gifcap

started time in 3 days

fork 3400442579/gifcap

Capture your screen to a GIF in your browser

https://gifcap.dev

fork in 4 days

startedjoaomoreno/gifcap

started time in 4 days

issue commentmicrosoft/vscode-vsce

Add --ignoreDependencies to package command

I was able to work around the issue by downgrading to npm@6 and recreating package-lock.json not to use lockfile version 2. Seems like a problem with the new lockfile version introduced with npm@7.

onilton

comment created time in 4 days