This package is still in alpha.

Web Frontend for trading strategy executor.

• This is a SvelteKit based frontend library
• Display active trading strategies
• Display open/closed trading position
• Show profitability metrics like profit and loss, trades won
• Explore trades

• Uses Bootstrap 4 for the layout (to be compatible with Trading Strategy frontend)

• Node.js 16+ (Array.at() used)

The package comes with a demo site with its .env configuration file. To get started with development do:

# Edit .env to point the environment to your trade executor instance
npm run dev

• src/lib contains reusable Svelte components to render trading strategy execution
• src/routes contains the default SvelteKit application pages. It needs to be copy-pasted to the parent project as is. This code is minimal and most of the code is in reusable components.

• Documenting Svelte components

• Rich Harris on creating SvelteKit libraries

SvelteKit does not support route re-use at the moment. To update routes in the main application:

• Update routes in trade-executor-frontend
• Copy-paste routes/strategy to frontend package
• Update frontend/package.json with all dependencies needed to run trade-executor-frontend

Each strategy executor is its own web server, with own domain.

The executor frontend must have id, name and URL configured for each executor.

For the demo app you can update URLs like this:

# Edit scripts/demo.env
source scripts/demo.env
echo $VITE_PUBLIC_STRATEGIES
# Edit .env

To make a new release…

npm version [major | minor | patch]
npm push
npm push --tags

TODO: add a GitHub action to automatically package and publish a release when a new tag is pushed.

In order to publish the package, you'll need to log into the GitHub package registry using a Personal Access Token (PAT). Follow the instructions outlined here

npm login --scope-@tradingstrategy-ai --registry=https://npm.pkg.github.com

> Username: USERNAME
> Password: TOKEN
> Email: PUBLIC-EMAIL-ADDRESS

You should only need to do this once (until your PAT expires). Once you're authenticated, you can publish the new package:

npm run package
(cd package && npm publish)