Minimal example making webpack and wasm/Emscripten work together.
Build instructions:
- Clone this gist
npm installnpm start- Open
http://localhost:8080 - Look at console
| 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/ |
Minimal example making webpack and wasm/Emscripten work together.
Build instructions:
npm installnpm starthttp://localhost:8080Minimal example making webpack and wasm/Emscripten work together.
Build instructions:
npm installnpm starthttp://localhost:8080(by @andrestaltz)
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.
| #!/usr/bin/env bash | |
| f() { | |
| # 获取当前仓库最新的状态,避免本地 tag 列表不是最新的 | |
| # https://stackoverflow.com/questions/8943693/can-git-operate-in-silent-mode | |
| # https://stackoverflow.com/questions/1204190/does-git-fetch-tags-include-git-fetch | |
| # https://stackoverflow.com/questions/16678072/can-we-set-a-git-default-to-fetch-all-tags-during-a-remote-pull | |
| git fetch --tags --prune --prune-tags --quiet | |
| local latestTag |
| 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) |
foobar, foo, bar, baz, qux, quux, corge, grault, garply, waldo, fred, plugh, xyzzy, thud
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.
# .bashrcerror while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
sudo apt-get install libnss3error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
sudo apt-get install libxss1