aeternity/aepp-base

Base æpp

Vue

42

3,214 commits

updated Sep 17, 2026

See the code

README

Base æpp

How to get the Base æpp

Also join our Telegram channel and our Forum.

Build Setup

# install dependencies
npm install

# serve with hot reload at http://localhost:8080/
npm run serve

# serve with hot reload at https://localhost:8080/
npm run serve -- --https

# run on android emulator or device
npm run serve:android

# run on ios emulator
npm run serve:ios

# build for production with minification
npm run build

# build for production and view the bundle analyzer report
npm run build -- --report

# build for cordova
npm run build:cordova

# build an app file
npm run build:ios

# build an apk file
npm run build:android

# run unit tests
npm run test:unit

# run e2e tests
npm run test:e2e

# run all tests
npm test

Contributing

We use the gitflow workflow this is also helpful.

  • Development of features happens in branches made from develop called feature/ like feature/show-token-balance.
  • When development is finished a pull request to develop is created. At least one person has to review the PR and when everything is fine the PR gets merged.
  • The develop branch gets deployed to the stage environment by travis.
  • To make a new release create a release branch called release/vX.X.X, also bump the version number in package.json in this branch.
  • Create a PR to master which then also has to be accepted.
  • Create a tag for this version and push the tag.
  • Also merge back the changes (like the version bump) into develop.
  • The master branch has to be deployed to the production environment manually.

Deployment

We have a stage (develop) and a production (master) branch and environments where these branches will be deployed to.

stage

  • Is used to see changes to the code in effect in a "real" environment without the fear of breaking the production environment.

production

  • Is the production environment, code lives in the "master" branch.

other branches

  • Every branch is auto-deployed on https://pr-<id>-base.stg.aepps.com/, where <id> is a number of PR.

unsigned .apk and .app file

bundle analyzer report

Contributors

davidyuk

2,100 commits

CedrikNikita

346 commits

etharner

285 commits

muxe

124 commits

aeternity/aepp-base

Base æpp

Vue

42

3,214 commits

updated Sep 17, 2026

See the code

README

Base æpp

How to get the Base æpp

Also join our Telegram channel and our Forum.

Build Setup

# install dependencies
npm install

# serve with hot reload at http://localhost:8080/
npm run serve

# serve with hot reload at https://localhost:8080/
npm run serve -- --https

# run on android emulator or device
npm run serve:android

# run on ios emulator
npm run serve:ios

# build for production with minification
npm run build

# build for production and view the bundle analyzer report
npm run build -- --report

# build for cordova
npm run build:cordova

# build an app file
npm run build:ios

# build an apk file
npm run build:android

# run unit tests
npm run test:unit

# run e2e tests
npm run test:e2e

# run all tests
npm test

Contributing

We use the gitflow workflow this is also helpful.

  • Development of features happens in branches made from develop called feature/ like feature/show-token-balance.
  • When development is finished a pull request to develop is created. At least one person has to review the PR and when everything is fine the PR gets merged.
  • The develop branch gets deployed to the stage environment by travis.
  • To make a new release create a release branch called release/vX.X.X, also bump the version number in package.json in this branch.
  • Create a PR to master which then also has to be accepted.
  • Create a tag for this version and push the tag.
  • Also merge back the changes (like the version bump) into develop.
  • The master branch has to be deployed to the production environment manually.

Deployment

We have a stage (develop) and a production (master) branch and environments where these branches will be deployed to.

stage

  • Is used to see changes to the code in effect in a "real" environment without the fear of breaking the production environment.

production

  • Is the production environment, code lives in the "master" branch.

other branches

  • Every branch is auto-deployed on https://pr-<id>-base.stg.aepps.com/, where <id> is a number of PR.

unsigned .apk and .app file

bundle analyzer report

Contributors

davidyuk

2,100 commits

CedrikNikita

346 commits

etharner

285 commits

muxe

124 commits

Languages

Vue

55.0%

JavaScript

43.3%