Joram van den Boezem

@OzairP cross posting this from https://github.com/dthree/vorpal/issues/334#issuecomment-466495091: > Quick update: there's an effort over at https://github.com/vorpaljs-reforged to _reforge_ vorpal by first porting it to TypeScript, update dependencies and maybe fix some...

@huan I'm one of the contributors to the vorpaljs-reforged project, but unfortunately, work on it has slowed down quite a bit in the last 6 months. The vorpal source code...

Is this possible to do natively with yargs? If yes, then it would be easy to support this scenario, too. Not sure though... If not, this should be added in...

Replacing `jQuery.event.handle` with `jQuery.event.dispatch` in http://github.com/stephband/jparallax/blob/master/js/jquery.event.frame.js#L101 worked for me!

I'm currently working on integrating the plugins from this respository into a custom GitHub Action to sync organisation defaults. For this purpose, it would have added value if the plugin...

This issue is making it impossible for us to use the same key for all repos in the same org, as described here https://docs.travis-ci.com/user/private-dependencies/#reusing-a-generated-key. Travis CI is an awesome tool,...

Don't want to leave GH. So now, every day, I pray to the GitHub Actions invite gods... 🙏

The proposed solution doesn't seem to work because `${{ inputs.node-version }}` is not evaluated in the `runs.image` context. 😞 I'm testing this on a fork here: https://github.com/hongaar/firebase-action/commit/bb149a96769f1f147c699ed3852e08b91bbdb271 Not sure if...

Closing this as there is a workaround (as long as values are unique): ```ts const options = [ { key: 1, value: "foo" }, { key: 2, value: "bar" }...

Still have this problem with npm 8.19.2: ``` node@9a0111889c1a: /workspaces/mokr on main [$] $ cat .npmrc workspaces = true node@9a0111889c1a: /workspaces/mokr on main [$] $ npm -v 8.19.2 node@9a0111889c1a: /workspaces/mokr...