Created
December 24, 2018 20:07
-
-
Save joejordan/2d17c02ff596632af6d10af6812a7597 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ℹ This is the configuration for your development deployment: | |
Ethereum Node: ws://localhost:8545 | |
ENS registry: 0x5f6f7e8cc7346a11ca2def8f827b7a0b612c56a1 | |
APM registry: aragonpm.eth | |
DAO address: 0xE9866fE6dF20F032E62Cc3094EdDe9748fE51753 | |
Opening http://localhost:3000/#/0xE9866fE6dF20F032E62Cc3094EdDe9748fE51753 to view your DAO | |
(node:12216) UnhandledPromiseRejectionWarning: Error: Error: Command failed: npm run start:local | |
sh: 1: copy-aragon-ui-assets: not found | |
npm ERR! Linux 4.15.0-43-generic | |
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "ui-assets" | |
npm ERR! node v8.10.0 | |
npm ERR! npm v3.5.2 | |
npm ERR! file sh | |
npm ERR! code ELIFECYCLE | |
npm ERR! errno ENOENT | |
npm ERR! syscall spawn | |
npm ERR! [email protected] ui-assets: `copy-aragon-ui-assets -n aragon-ui ./build` | |
npm ERR! spawn ENOENT | |
npm ERR! | |
npm ERR! Failed at the [email protected] ui-assets script 'copy-aragon-ui-assets -n aragon-ui ./build'. | |
npm ERR! Make sure you have the latest version of node.js and npm installed. | |
npm ERR! If you do, this is most likely a problem with the aragon package, | |
npm ERR! not with npm itself. | |
npm ERR! Tell the author that this fails on your system: | |
npm ERR! copy-aragon-ui-assets -n aragon-ui ./build | |
npm ERR! You can get information on how to open an issue for this project with: | |
npm ERR! npm bugs aragon | |
npm ERR! Or if that isn't available, you can get their info via: | |
npm ERR! npm owner ls aragon | |
npm ERR! There is likely additional logging output above. | |
npm ERR! Please include the following file with any support request: | |
npm ERR! /home/joe/.aragon/wrapper-2d79d2b9373d8b89bb28a7ecd613fb6373ac2d43/npm-debug.log | |
child_process.js:644 | |
throw err; | |
^ | |
Error: Command failed: | |
npm run ui-assets && | |
REACT_APP_PACKAGE_VERSION=0.6.0 parcel serve src/index.html --port 3000 --out-dir ./build --no-cache | |
at checkExecSyncError (child_process.js:601:13) | |
at execSync (child_process.js:641:13) | |
at Object.<anonymous> (/home/joe/.aragon/wrapper-2d79d2b9373d8b89bb28a7ecd613fb6373ac2d43/scripts/start:12:1) | |
at Module._compile (module.js:652:30) | |
at Object.Module._extensions..js (module.js:663:10) | |
at Module.load (module.js:565:32) | |
at tryModuleLoad (module.js:505:12) | |
at Function.Module._load (module.js:497:3) | |
at Function.Module.runMain (module.js:693:10) | |
at startup (bootstrap_node.js:188:16) | |
npm ERR! Linux 4.15.0-43-generic | |
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start" | |
npm ERR! node v8.10.0 | |
npm ERR! npm v3.5.2 | |
npm ERR! code ELIFECYCLE | |
npm ERR! [email protected] start: `scripts/start` | |
npm ERR! Exit status 1 | |
npm ERR! | |
npm ERR! Failed at the [email protected] start script 'scripts/start'. | |
npm ERR! Make sure you have the latest version of node.js and npm installed. | |
npm ERR! If you do, this is most likely a problem with the aragon package, | |
npm ERR! not with npm itself. | |
npm ERR! Tell the author that this fails on your system: | |
npm ERR! scripts/start | |
npm ERR! You can get information on how to open an issue for this project with: | |
npm ERR! npm bugs aragon | |
npm ERR! Or if that isn't available, you can get their info via: | |
npm ERR! npm owner ls aragon | |
npm ERR! There is likely additional logging output above. | |
npm ERR! Please include the following file with any support request: | |
npm ERR! /home/joe/.aragon/wrapper-2d79d2b9373d8b89bb28a7ecd613fb6373ac2d43/npm-debug.log | |
npm ERR! Linux 4.15.0-43-generic | |
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "start:local" | |
npm ERR! node v8.10.0 | |
npm ERR! npm v3.5.2 | |
npm ERR! code ELIFECYCLE | |
npm ERR! [email protected] start:local: `scripts/launch-local.sh` | |
npm ERR! Exit status 1 | |
npm ERR! | |
npm ERR! Failed at the [email protected] start:local script 'scripts/launch-local.sh'. | |
npm ERR! Make sure you have the latest version of node.js and npm installed. | |
npm ERR! If you do, this is most likely a problem with the aragon package, | |
npm ERR! not with npm itself. | |
npm ERR! Tell the author that this fails on your system: | |
npm ERR! scripts/launch-local.sh | |
npm ERR! You can get information on how to open an issue for this project with: | |
npm ERR! npm bugs aragon | |
npm ERR! Or if that isn't available, you can get their info via: | |
npm ERR! npm owner ls aragon | |
npm ERR! There is likely additional logging output above. | |
npm ERR! Please include the following file with any support request: | |
npm ERR! /home/joe/.aragon/wrapper-2d79d2b9373d8b89bb28a7ecd613fb6373ac2d43/npm-debug.log | |
> [email protected] start:local /home/joe/.aragon/wrapper-2d79d2b9373d8b89bb28a7ecd613fb6373ac2d43 | |
> scripts/launch-local.sh | |
Running aragon/aragon on local environment settings... | |
Found a local IPFS daemon running... | |
The app will be configured to connect and serve assets from from the default gateway (http://localhost:8080/ipfs). | |
Also defaulting the asset bridge to IPFS. | |
> [email protected] start /home/joe/.aragon/wrapper-2d79d2b9373d8b89bb28a7ecd613fb6373ac2d43 | |
> scripts/start | |
> [email protected] ui-assets /home/joe/.aragon/wrapper-2d79d2b9373d8b89bb28a7ecd613fb6373ac2d43 | |
> copy-aragon-ui-assets -n aragon-ui ./build | |
at /usr/local/lib/node_modules/@aragon/cli/dist/commands/run.js:412:29 | |
at <anonymous> | |
at process._tickCallback (internal/process/next_tick.js:188:7) | |
(node:12216) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3) | |
(node:12216) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment