falcon11

React recently introduced an experimental profiler API. This page gives instructions on how to use this API in a production release of your app.

Table of Contents

• Profiling in production
  • Create React App
  • Webpack 4
• Troubleshooting
  • Tracing broke after an NPM update

Profiling in production

falcon11

// Created by Chih.Lun.Kang
// 網路上找的範例大部分都不能用，後來嘗試數次只有這方法可行
// 主網的appid => 539ab33xxxx，要去Infura申請，在上面建立一個project
// ####  NOTE  #### : 要特別注意本身轉帳的帳號要儲備足夠數量的 eth 跟 btc 
// ####  注意  #### : 目前使用人工轉換儲值手續費，建議在幣價好的時候一次換匯才划算

const USDTJSON = require('./build/contracts/USDT.json')
const Web3 = require('web3')
const Tx = require('ethereumjs-tx').Transaction

falcon11

//
//  Use this file to import your target's public headers that you would like to expose to Swift.
//

void anti_gdb_debug(void);
int checkJailBroken(void);

falcon11

Original Link

Imagine that you cloned an open source project to contribute something. You implemented a bugfix through a series of atomic commits on a private branch. Just when you’re about to create a Pull Request to submit your changes, you discover in the contributor’s guide that you’re supposed to prefix each commit with the bug tracking number.

Rewriting the commit message of the last commit is easy:

git commit --amend

falcon11

#!/usr/bin/env python

## Dependencies:
#
# pip install qiniu
# 
## Tips for Deploy certs to Qiniu:
# 
# export DOMAIN=lewangdev.com
# export QINIU_DOMAIN=images.${DOMAIN},staticfiles.${DOMAIN}