Why is necessary to use async and await for the component methods?

ie:
async componentWillMount() {

Is this because of ethereum?

$ npm run geth

[email protected] geth /Users/kabeer.jalaluddin/Desktop/Node Js Tutorials/TruffleProjects/ethereum-todolist-master
gulp geth

[12:03:38] Using gulpfile ~/Desktop/Node Js Tutorials/TruffleProjects/ethereum-todolist-master/gulpfile.js
[12:03:38] Starting 'geth'...
[12:03:39] Finished 'geth' after 14 ms
WARN [04-25|12:03:39] No etherbase set and no accounts found as default
INFO [04-25|12:03:39] Allocated cache and file handles database="/Users/kabeer.jalaluddin/Desktop/Node Js Tutorials/TrufflePr
ojects/ethereum-todolist-master/blockchain/geth/chaindata" cache=16 handles=16
INFO [04-25|12:03:39] Successfully wrote genesis state database=chaindata
hash=ba4fe4…dc83a6
INFO [04-25|12:03:39] Allocated cache and file handles database="/Users/kabeer.jalaluddin/Desktop/Node Js Tutorials/TrufflePr

ojects/ethereum-todolist-master/blockchain/geth/lightchaindata" cache=16 handles=16
INFO [04-25|12:03:39] Successfully wrote genesis state database=lightchaindata
hash=ba4fe4…dc83a6
WARN [04-25|12:03:39] No etherbase set and no accounts found as default
INFO [04-25|12:03:39] Starting peer-to-peer node instance=Geth/v1.7.3-stable/darwin-amd64/go1.9.2
INFO [04-25|12:03:39] Allocated cache and file handles database="/Users/kabeer.jalaluddin/Desktop/Node Js Tutorials/TrufflePr
ojects/ethereum-todolist-master/blockchain/geth/chaindata" cache=128 handles=1024
INFO [04-25|12:03:39] Initialised chain configuration config="{ChainID: Homestead: DAO: DAOSupport: false
EIP150: EIP155: EIP158: Byzantium: Engine: unknown}"
INFO [04-25|12:03:39] Disk storage enabled for ethash caches dir="/Users/kabeer.jalaluddin/Desktop/Node Js Tutorials/TruffleProject
s/ethereum-todolist-master/blockchain/geth/ethash" count=3
INFO [04-25|12:03:39] Disk storage enabled for ethash DAGs dir=/Users/kabeer.jalaluddin/.ethash
count=2
INFO [04-25|12:03:39] Initialising Ethereum protocol versions="[63 62]" network=1999
INFO [04-25|12:03:39] Loaded most recent local header number=0 hash=ba4fe4…dc83a6 td=1024
INFO [04-25|12:03:39] Loaded most recent local full block number=0 hash=ba4fe4…dc83a6 td=1024
INFO [04-25|12:03:39] Loaded most recent local fast block number=0 hash=ba4fe4…dc83a6 td=1024
INFO [04-25|12:03:39] Loaded local transaction journal transactions=0 dropped=0
INFO [04-25|12:03:39] Regenerated local transaction journal transactions=0 accounts=0
INFO [04-25|12:03:39] Starting P2P networking
INFO [04-25|12:03:39] RLPx listener up self="enode://d758362ecc5a39c42b377294cb9c50a413a1b5c759178eaf0dc1f11c
6dc94b33071fdaf9417597d71e1f8f3d37d4fa9c880ec3f363b4b2bac4e765a2c998f603@[::]:30303?discport=0"
INFO [04-25|12:03:39] Blockchain manager stopped
INFO [04-25|12:03:39] Stopping Ethereum protocol
INFO [04-25|12:03:39] Ethereum protocol stopped
INFO [04-25|12:03:39] Transaction pool stopped

INFO [04-25|12:03:39] Database closed database="/Users/kabeer.jalaluddin/Desktop/Node Js Tutorials/TrufflePr
ojects/ethereum-todolist-master/blockchain/geth/chaindata"
Fatal: Error starting protocol stack: listen unix /Users/kabeer.jalaluddin/Desktop/Node Js Tutorials/TruffleProjects/ethereum-todolis
t-master/blockchain/geth.ipc: bind: invalid argument

events.js:137
throw er; // Unhandled 'error' event
^
Error: Command geth --rpc --rpcport "8545" --rpccorsdomain "*" --datadir "blockchain" --rpcapi "db,eth,net,web3" --nodiscover --netw orkid 1999 console failed with exit code 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] geth: gulp geth
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] geth script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/kabeer.jalaluddin/.npm/_logs/2018-04-25T04_03_41_304Z-debug.log

2018-04-25T04_10_27_641Z-debug.log

Works fine with testrpc but this issue is also there

Bug Report

Description

When creating a new todo, the scenario that the transaction is revoked due to chain reorganization is not considered.
When the transaction is executed but then revoked, the todo item still shows on the UI which will make the subsequent transaction that aims to delete it fails, losing user's transaction fee.

Reproduce Steps

1. send transaction to create a new todo
2. When the transaction is executed, UI shows the new todo
3. Let blockchain reorganize by importing a side chain
4. The transaction is revoked and returns to transaction pool.
5. The todo item still shows in UI.
6. Now if we try to delete the item by click x, the transaction will always fail.

Expected Behaviour

If the transactions revoked by chain reorganization, the todo item in UI should be removed accordingly.