Skip to content

Conversation

sheremet-va
Copy link
Member

Description

Fixes #8523

This guide needs some love, putting it in a draft until I can give it more time.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
  • Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Copy link

netlify bot commented Sep 3, 2025

Deploy Preview for vitest-dev ready!

Name Link
🔨 Latest commit 0d00650
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/68b8087b6fac0100088c0c09
😎 Deploy Preview https://deploy-preview-8524--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link

@mike-lischke mike-lischke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

Copy link
Member

@AriPerkkio AriPerkkio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

## Extending Built-in Reporters
In general, you don't need to create your reporter from scratch. `vitest` comes with several default reporting programs that you can extend.
```ts
import { DefaultReporter } from 'vitest/reporters'
export default class MyDefaultReporter extends DefaultReporter {
// do something
}
```

This is quite bad as it makes reporters part of public API. I think we've broken their public API many times in the past.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SyntaxError: The requested module '.../node_modules/vitest/dist/reporters.js' does not provide an export named 'BaseReporter'
3 participants