The @leanup stack only contains the selected tools and their default configuration. No specific things are implemented, such as a dedicated CLI.

This means that all commands for developing, testing or building etc. the app relate to the configuration of the npm scripts.


The following table lists the scripts tags available for npm scripts:

npm run <script tag>

script tagcommand line execution
reinstallnpm run remove && npm install
updatencu -t minor -u && npm install && ncu
previewvite preview --open
formatprettier --check {src,tests}/**
lintnpm run lint:eslint && npm run lint:tsc
lint:eslinteslint {src,tests}/**/*.{html,js,json,jsx,ts,tsx,gql,graphql}
lint:tsctsc -p tsconfig.json
testcross-env NODE_ENV=test mocha
coveragecross-env NODE_ENV=test nyc mocha
removerm -rf node_modules package-lock.json
buildcross-env NODE_ENV=production webpack
servecross-env NODE_ENV=development webpack serve --devtool=source-map --no-live-reload --hot
startnpm run serve -- --open=chrome
cucumber*cross-env NIGHTWATCH_ENV=chrome cucumber-js tests/cucumber/features/**/*.feature --require @babel/register --require cucumber.conf.js --require tests/cucumber/step-definitions --format node_modules/cucumber-pretty --format json:.reports/cucumber/report.json

* This script tags are experimental.