menu

Aragon

Aragon is the most powerful and modular way to run DAOs

Channels
# All channels
view-forward
# Announcements
view-forward
# App development
view-forward
# Aragon Agent
view-forward
# Aragon Client
view-forward
# Aragon Connect
view-forward
# aragonOS
view-forward
# aragonUI
view-forward
# Feature requests
view-forward
Team

unable to create boilerplate app

April 27, 2020 at 1:01pm

unable to create boilerplate app

April 27, 2020 at 1:01pm (Edited 3 months ago)
I am trying to create a sandboxed environment in virtual box to hack on aragon apps. I am unable to npx create-aragon-app I am not sure if there is a problem with the new Ubuntu LTS or if I m making a mistake provisioning the environment.
System: 'Ubuntu budgie 20.04 LTS' setup: sudo apt-get update && sudo apt-get upgrade sudo apt install build-essential git python curl nvim curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash nvm install 12.16.2
Fails at: npx create-aragon-app foo
An unexpected error occurred:
Error: Cannot find module 'solidity-parser-antlr'
Require stack:
- /home/aaron/projects/foo/node_modules/@aragon/buidler-aragon/dist/src/utils/ast/parseContractFunctions.js
- /home/aaron/projects/foo/node_modules/@aragon/buidler-aragon/dist/src/utils/ast/index.js
- /home/aaron/projects/foo/node_modules/@aragon/buidler-aragon/dist/src/utils/artifact/generateAragonArtifact.js
- /home/aaron/projects/foo/node_modules/@aragon/buidler-aragon/dist/src/utils/artifact/index.js
- /home/aaron/projects/foo/node_modules/@aragon/buidler-aragon/dist/src/tasks/publish/index.js
- /home/aaron/projects/foo/node_modules/@aragon/buidler-aragon/dist/src/index.js
- /home/aaron/projects/foo/node_modules/@nomiclabs/buidler/internal/core/plugins.js
- /home/aaron/projects/foo/node_modules/@nomiclabs/buidler/internal/core/config/config-loading.js
- /home/aaron/projects/foo/node_modules/@nomiclabs/buidler/internal/cli/cli.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:980:15)
at Function.Module._resolveFilename (/home/aaron/projects/foo/node_modules/tsconfig-paths/lib/register.js:75:40)
at Function.Module._load (internal/modules/cjs/loader.js:862:27)
at Module.require (internal/modules/cjs/loader.js:1042:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object.<anonymous> (/home/aaron/projects/foo/node_modules/@aragon/buidler-aragon/src/utils/ast/parseContractFunctions.ts:3:1)
at Module._compile (internal/modules/cjs/loader.js:1156:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
at Module.load (internal/modules/cjs/loader.js:1000:32)
at Function.Module._load (internal/modules/cjs/loader.js:899:14)
at Module.require (internal/modules/cjs/loader.js:1042:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object.<anonymous> (/home/aaron/projects/foo/node_modules/@aragon/buidler-aragon/src/utils/ast/index.ts:1:1)
at Module._compile (internal/modules/cjs/loader.js:1156:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
at Module.load (internal/modules/cjs/loader.js:1000:32)
at Function.Module._load (internal/modules/cjs/loader.js:899:14)
at Module.require (internal/modules/cjs/loader.js:1042:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object.<anonymous> (/home/aaron/projects/foo/node_modules/@aragon/buidler-aragon/src/utils/artifact/generateAragonArtifact.ts:7:1)
at Module._compile (internal/modules/cjs/loader.js:1156:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] compile: `buidler compile --force`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] compile 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! /home/aaron/.npm/_logs/2020-04-27T12_55_06_133Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `npm run compile && npm run copy-artifacts && npm run build-app`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall 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! /home/aaron/.npm/_logs/2020-04-27T12_55_06_170Z-debug.log
Failed to install dependencies. See above output.

April 27, 2020 at 9:18pm
Oh this is awkward, npm couldn't find a dependency (solidity-parser-antlr).
Could you try again?
  • reply
  • like

April 28, 2020 at 6:36am
thanks Brett
  • reply
  • like
Hi, I had the same problem, it was solved when I installed yarn.
  • reply
  • like
That seems weird... if you don't mind , , what does npm install solidity-parser-antlr do in a npm project for you? It should definitely be installing 😅.
  • reply
  • like

April 29, 2020 at 7:07am
I can install solidity-parser-antlr in a separate project. It seems that the problem is the yarn.lock file, and causes problems when using npm.
  • reply
  • like

May 7, 2020 at 4:11am
Hi, the problem should be fixed with the latest version of /buidler-aragon. You can either run npx create-aragon-app again or upgrade buidler-aragon (npm i /[email protected]^0.2.4 --save-dev) in an existing app.
  • reply
  • like

May 7, 2020 at 9:55pm
I had the same problem, it was solved when I installed yarn.
same i have had the same issue happen again but i think it was because i was using both yarn and npm
  • reply
  • like

May 8, 2020 at 2:07pm
Did you have the problem again after the update to 0.2.4?
  • reply
  • like

May 9, 2020 at 1:30pm
That seems weird... if you don't mind , , what does npm install solidity-parser-antlr do in a npm project for you? It should definitely be installing 😅.
installed it and the problem went away :D
Edited
  • reply
  • like
I removed solidity-parser-antlr and upgraded to buidler-aragon 0.2.5 got new dependency errors. Error BDLR802: Plugin /buidler-aragon requires /buidler version ^1.3.2 but got 1.2.0 same with the etherscan and truffle dev dependencies. But after updating those manually, it all works as expected
Edited
  • reply
  • like

May 11, 2020 at 3:37am
Hi Aaron, are you using npm or yarn?
  • reply
  • like
im using yarn but my reflex is to use npm so sometimes i use that. do you think that is the issue
  • reply
  • like
Ah it might be that there were older dependencies leftover. Can you delete your node_modules folder along with any package-lock.json and yarn.lock files and re-install?
like-fill
1
  • reply
  • like
yup that works a treat
like-fill
1
  • reply
  • like