流浪大法师 liuliangsir

Use Proxy for Git/GitHub

Generally, the Git proxy configuration depends on the Git Server Protocol you use. And there're two common protocols: SSH and HTTP/HTTPS. Both require a proxy setup already. In the following, I assume a SOCKS5 proxy set up on localhost:1080. But it can also be a HTTP proxy. I'll talk about how to set up a SOCKS5 proxy later.

SSH Protocol

When you do git clone ssh://[user@]server/project.git or git clone [user@]server:project.git, you're using the SSH protocol. You need to configurate your SSH client to use a proxy. Add the following to your SSH config file, say ~/.ssh/config:

ProxyCommand nc -x localhost:1080 %h %p

Some things that are "better" with this BetterPromise implementation:

BetterPromise # then(..) accepts a BetterPromise (or Promise) instance passed directly, instead of requiring a function to return it, so that the promise is linked into the chain.
```
var p = BetterPromise.resolve(42);

var q = Promise.resolve(10);

p.then(console.log).then(q).then(console.log);
```

Minimal example making webpack and wasm/Emscripten work together.

Build instructions:

Clone this gist
npm install
npm start
Open http://localhost:8080
Look at console

First, Download and install the newest version of Meld for Windows. https://download.gnome.org/binaries/win32/meld/

Next we need to edit your .gitconfig file. This file lives as a hidden file in your user directory. Here is a sample of mine:

[user]
	email = [email protected]
	name = Sir Kuttin
[merge]

Strings

`String.prototype.*`

None of the string methods modify this – they always return fresh strings.

charAt(pos: number): string ^ES1

Returns the character at index pos, as a string (JavaScript does not have a datatype for characters). str[i] is equivalent to str.charAt(i) and more concise (caveat: may not work on old engines).

How to solve `dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.60.dylib`

brew uninstall --ignore-dependencies node icu4c
brew install node

This content moved here: https://exploringjs.com/impatient-js/ch_arrays.html#quickref-arrays

Steps to publish a npm package to beta that won't be available via latest and won't auto install on ncu updates etc

Ensure any compile is run npm run dist etc
Modify version in package.json to the following format (match with existing verion numbers etc) "version": "0.1.120-beta.1" where beta.x is the number of those betas
Publish to npm npm publish --tag beta

There are two options for install:

Always install beta with npm install packagename@beta
Install specific version with npm install [email protected]

	#!/bin/bash
	# With create-react-app, a self signed (therefore invalid) certificate is generated.
	# 1. Create some folder in the root of your project
	# 2. Copy your valid development certificate to this folder
	# 3. Copy this file to the same folder
	# 4. In you package.json, under `scripts`, add `postinstall` script that runs this file.
	# Every time a user runs npm install this script will make sure to copy the certificate to the
	# correct location

	TARGET_LOCATION="./node_modules/webpack-dev-server/ssl/server.pem"

	# Reference: https://www.exclamationlabs.com/blog/continuous-deployment-to-npm-using-gitlab-ci/

	# GitLab uses docker in the background, so we need to specify the
	# image versions. This is useful because we're freely to use
	# multiple node versions to work with it. They come from the docker
	# repo.
	# Uses NodeJS V 9.4.0
	image: node:9.4.0

	# And to cache them as well.