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:
npm install
npm start
http://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.
# .bashrc
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
Your name and email address were configured automatically based | |
on your username and hostname. Please check that they are accurate. | |
You can suppress this message by setting them explicitly: | |
git config --global user.name "Your Name" | |
git config --global user.email [email protected] | |
After doing this, you may fix the identity used for this commit with: | |
git commit --amend --reset-author |
The package linked to from here is now pure ESM. It cannot be require()
'd from CommonJS.
This means you have the following choices:
import foo from 'foo'
instead of const foo = require('foo')
to import the package. You also need to put "type": "module"
in your package.json and more. Follow the below guide.await import(…)
from CommonJS instead of require(…)
.