-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
docs: add Profiling Test Performance guide #6555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add Profiling Test Performance guide #6555
Conversation
✅ Deploy Preview for vitest-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
39412fe to
1b72c3e
Compare
|
This should be merged without squash to get |
hi-ogawa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, so comprehensive! I tested a profile example and it's very nice!
1b72c3e to
33d7067
Compare
33d7067 to
95b001d
Compare
95b001d to
999502d
Compare
|
This looks awesome! Thank you! |
When release is done, let's manually add the |
Description
Contains two separate commits. Should be merged without squash.
fix(forks): --cpu-prof and --heap-prof not workingnode:child_process.forkdoes not generate cpu-prof when process is killed nodejs/node#55094 when diagnostic exec args are detecteddocs: add Profiling Test Performance guidePlease don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yamlunless you introduce a new test example.Tests
pnpm test:ci.Documentation
pnpm run docscommand.Changesets
feat:,fix:,perf:,docs:, orchore:.