Skip to content

chore: fix typos across codebase #7

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Jun 18, 2025
Merged

chore: fix typos across codebase #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0b43c0b
fix typo in README regarding Vitest Browser Mode
rubenpenap Jun 17, 2025
e4fa7c6
fix typo in README regarding redundancy in browser-like environments
rubenpenap Jun 17, 2025
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@

## Prerequisites

You don't have to have any prior experience with Vitest or Vitest Broweser Mode
You don't have to have any prior experience with Vitest or Vitest Browser Mode
to complete this workshop.

- **A basic experience with TypeScript is required.**
Expand Down
2 changes: 1 addition & 1 deletion exercises/01.sunsetting-jsdom/README.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,6 @@ About 15 years ago JSDOM set off to solve the lack of proper tooling for integra

> 📜 If you want to learn more about the dangers of browser-like environments, read [Why I Won't Use JSDOM](https://www.epicweb.dev/why-i-won-t-use-jsdom).

But it's not about being redudant. Browser-like environment pose a serious threat to the quality of your tests, have compatibility issues, and can break valid JavaScript code. This often leads to you wasting your time debugging your test environment instead of developing and testing your apps.
But it's not about being redundant. Browser-like environment pose a serious threat to the quality of your tests, have compatibility issues, and can break valid JavaScript code. This often leads to you wasting your time debugging your test environment instead of developing and testing your apps.

I don't want you to waste your time on that. I want you to write solid tests and you can trust, and good tooling is an essential element of that experience.