Good practice workflow for framework developers

[krausest]

This discussion should help framework developers to find a good workflow to check the impact of changes:

Prepare:

1. Checkout js-framework-benchmark (it's okay to checkout master)
2. run npm ci && npm run install-local
3. Download the build.zip from the latest release, put it in the js-framework-benchmark directory and unzip build.zip
4. Start the server vianpm startand keep it running in the background
5. Check: http://localhost:8080/frameworks/keyed/svelte should now work in the browser

Run peer group:

1. You can either run all frameworks (takes about 16 hours) or just run selected frameworks: open a new console window cd webdriver-ts and keep that console window open
2. run e.g. `npm run bench keyed/vanillajs keyed/svelte keyed/solid keyed/react'
3. create the results table npm run results and open the results http://localhost:8080/webdriver-ts-results/table.html

Develop:

1. Create or copy an implementation and start developing in frameworks/keyed/${your-implemenation-name} (or non-keyed)
2. Open a separate console window, cd to that directory and keep it open
3. Use npm install (and delete node_modules and package-lock.json when appropriate to check that dependencies are really clean)
4. Make changes and recompile e.g. with npm run build-prod in that directory
5. Run a single benchmark (need to be run in webdriver-ts directory, use the console window you opened in "run peer group"):npm run bench -- --benchmark 03_ --framework keyed/${your-implemenation-name}. The benchmark runner logs the duration for each benchmark run, the mean, the median and so an. This might already be enough to see if the change helped. All benchmarks can be run with that number 01_, 02_, .. for the CPU benchmarks, 21_,22_ for the the mem benchmarks and 30_ for the startup benchmark (I know the number scheme isn't really logical).
   Alternatively you can run the whole benchmark just for your framework npm run bench keyed/${your-implemenation-name} and update the table (run npm run results in webdriver-ts). Then you can open the table again.