流浪大法师 liuliangsir

puppeteer dependeces in ubuntu 18.04 (Bionic)

error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

sudo apt-get install libnss3

error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory

sudo apt-get install libxss1

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

foobar, foo, bar, baz, qux, quux, corge, grault, garply, waldo, fred, plugh, xyzzy, thud

ASCII.jp：技術文書に頻出する「foobar」って何だ？｜今さら聞けないIT英語

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

Git Submodules basic explanation

Why submodules?

In Git you can add a submodule to a repository. This is basically a repository embedded in your main repository. This can be very useful. A couple of advantages of using submodules:

You can separate the code into different repositories.

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

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

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]

	CULTURE SPEC.CULTURE ENGLISH NAME
	--------------------------------------------------------------
	Invariant Language (Invariant Country)
	af af-ZA Afrikaans
	af-ZA af-ZA Afrikaans (South Africa)
	ar ar-SA Arabic
	ar-AE ar-AE Arabic (U.A.E.)
	ar-BH ar-BH Arabic (Bahrain)
	ar-DZ ar-DZ Arabic (Algeria)
	ar-EG ar-EG Arabic (Egypt)

	git clone --recursive https://github.com/WebAssembly/wabt
	cd wabt

	make
	make clang-debug
	make gcc-i686-release
	make clang-debug-lsan
	make gcc-debug-no-re2c

	chmod +x bin/