In your command-line run the following commands:
brew doctor
brew update
#!/bin/bash | |
if [ "$#" -lt 1 ]; then | |
echo "$# is Illegal number of parameters." | |
echo "Usage: $0 http://example.org" | |
exit 1 | |
fi | |
SERVER=$1 |
In your command-line run the following commands:
brew doctor
brew update
=============================================================================== | |
= 빔 길잡이 (VIM Tutor) 에 오신 것을 환영합니다 - Version 1.5 = | |
=============================================================================== | |
빔(Vim)은 이 길잡이에서 다 설명할 수 없을 만큼 많은 명령을 가진 | |
매우 강력한 편집기입니다. 이 길잡이는 빔을 쉽게 전천후 편집기로 사용할 | |
수 있도록 충분한 명령에 대해 설명하고 있습니다. | |
이 길잡이를 떼는 데에는 실습하는 데에 얼마나 시간을 쓰는 가에 따라서 | |
25-30 분 정도가 걸립니다. |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
React introduced shallow rendering in 0.13. This is an excellent feature that I wish was included earlier in React. It aims to solve the problem of unit testing components without going through a real, or jsdom mocked, DOM. I couldn't find any info online about what lifecycle events it actually fires. So I did some testing of my own. To reproduce, put component.js
and test.js
into a folder and run node test.js
.
TLDR; shallow rendering only invokes the following lifecycle hooks (in order):
getDefaultProps
getInitialState
componentWillMount
stops here until re-rendercomponentWillReceiveProps
shouldComponentUpdate
componentWillUpdate
Lifecycle: | Update: | |
Mounting and Unmounting | New Props or State | |
--------------------------------+----------------------------------- | |
| | |
getDefaultProps() | componentWillReceiveProps()* | |
| | |
getInitialState() | shouldComponentUpdate() | |
| | |
componentWillMount() | componentWillUpdate() | |
| |
[ | |
{ | |
"city": "New York", | |
"growth_from_2000_to_2013": "4.8%", | |
"latitude": 40.7127837, | |
"longitude": -74.0059413, | |
"population": "8405837", | |
"rank": "1", | |
"state": "New York" | |
}, |
# first: | |
lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom | while read f; do sudo rm /usr/local/${f}; done | |
sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.* | |
# To recap, the best way (I've found) to completely uninstall node + npm is to do the following: | |
# go to /usr/local/lib and delete any node and node_modules | |
cd /usr/local/lib | |
sudo rm -rf node* |