da47225efe
* Add benchmarking for the dev server This adds benchmarking for the dev server. * Use fs.rm instead * Only rimraf if the folder exists * Make uncached match CI * Change the cached time too * Don't run benchmark in CI * Switch back test command * Make tests be within 10 percent * Use yarn to run multiple things * Turn benchmark into uvu tests * Debugging benchmark * Print chunk for testing * Ignore benchmark folder in uvu * Add build benchmarking * Update benchmark numbers
1.3 KiB
Contributing
Making Pull Requests
When making a pull request, add a changeset which helps with releases.
yarn changeset
This will prompt you asking what type of change was made.
Releases
For those contributors that have access to publish to npm, the following is how you do releases.
From the main branch do a pull, install and build:
git pull origin main
yarn install
yarn build
Then bump the versions:
yarn changeset version
This should change package.json bumping version numbers and update changelogs. Inspect these to make sure they are what you expect.
Commit and push these changes, then run an npm publish for each of the packages that have changed.
Important! Ordering publishes can be important. If
astro-parserchanges you should publish that beforeastro, for example.
cd packages/astro
npm publish
Running benchmarks
We have benchmarks to keep performance under control. You can run these by running (from the project root):
yarn workspace astro run benchmark
Which will fail if the performance has regressed by 10% or more.
To update the times cd into the packages/astro folder and run the following:
node test/benchmark/build.bench.js --save
node test/benchmark/dev.bench.js --save
Which will update the build and dev benchmarks.