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
startnpm run vite:start
servenpm run vite:serve
buildnpm run webpack:build
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
snowpack:build*snowpack build
snowpack:serve*npm run snowpack:start -- --open none
snowpack:start*snowpack dev
vite:build*vite build
vite:start*npm run vite:serve -- --open
webpack:buildcross-env NODE_ENV=production webpack
webpack:servecross-env NODE_ENV=development webpack serve --devtool=source-map
webpack:startnpm run webpack: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.