159 Commits

Author	SHA1	Message	Date
emizzle	6fe162a8da	Fix issues with missing web3 dependencies ... The issue was the npm dependency graph was causing the web3 dependencies to be nested inside the `node_modules/web3/node_modules` folder. After removing web3 from `package-lock.json`, and allowing npm to rebuild the graph with `npm install`, the web3 depedencies (ie web3-bzz) were correctly installed at the same level as web3. However, this also introduced a new dependency issue in that web3-providers-ws required and depended on the websocket package at a specific github commit and was causing the same issue with websocket being installed at `node_modules/web3-providers-ws/node_modules/websocket`. Removing the web3-providers-ws dependency on websocket and replacing with version 1.0.25 requirement brought the websocket package back to the same level as web3.	2018-04-26 15:08:37 +10:00
Jonathan Rainville	df5b647ecb	fix and add tests	2018-04-19 15:25:27 -04:00
Jonathan Rainville	5ca9dd73de	package locks	2018-04-18 15:04:04 -04:00
Jonathan Rainville	2568ec1aec	implement the download function	2018-04-17 16:34:37 -04:00
Richard Ramos	f56b42d91f	Linting	2018-04-05 11:41:28 -04:00
Iuri Matias	94887f933d	update finalhandler npm package	2018-03-30 12:47:15 -04:00
Iuri Matias	6cafb319ac	update commander, css-loader, ejs packages	2018-03-30 12:07:58 -04:00
Iuri Matias	66187aef9a	update eslint version	2018-03-30 11:48:35 -04:00
Iuri Matias	a8e22ec45c	move demo and boilerplate to a templates folder	2018-03-29 19:23:24 -04:00