test: fix various typos across codebase

[JamBalaya56562]

Summary by Sourcery

Fix typos and spelling mistakes across the test suite to improve readability and correctness

Tests:

• Correct spelling in test descriptions, comments, error messages, and snapshots across unit, integration, and e2e tests

Chores:

• Rename mispelled variables and identifiers (e.g. entrypointsSubscription, Component) and update import and identifier names for consistency

[sourcery-ai]

Reviewer's Guide

This PR fixes a wide range of typos across the test suite by renaming variables, correcting string literals, and updating import and comment spellings to ensure consistency.

File-Level Changes

Change	Details	Files
Standardize subscription variable name in next-rs-api tests	Rename entrypointsSubscribtion to entrypointsSubscription Update await() and return() calls to use the corrected variable	test/development/basic/next-rs-api.test.ts
Correct typos in serialization tests	Fix .leve1 path to .level1 in error snapshots Update object keys from leve1 to level1	test/unit/is-serializable-props.test.ts
Fix WASM instantiate spelling in edge-runtime dynamic code	Rename wasmInstanciate to wasmInstantiate and wasmBufferInstanciate to wasmBufferInstantiate in utils Update middleware and API route handlers to use the corrected keys	test/integration/edge-runtime-dynamic-code/lib/utils.js test/integration/edge-runtime-dynamic-code/middleware.js test/integration/edge-runtime-dynamic-code/pages/api/route.js
Correct import and component naming	Change import Compoment to Component Update JSX usage <Compoment /> to <Component />	test/e2e/app-dir/resource-url-encoding/app/page.tsx
Bulk spelling fixes in test descriptions, comments, and literals	Replace immedately with immediately Correct various misspellings like diallows → disallows, continously → continuously, treshold → threshold, unintialized → uninitialized Fix comment and test title typos across multiple suites	test/e2e/app-dir/segment-cache/revalidation/segment-cache-revalidation.test.ts test/e2e/app-dir/app-static/app-static.test.ts test/e2e/app-dir/node-extensions/node-extensions.random.test.ts test/unit/accept-headers.test.ts test/lib/add-redbox-matchers.ts test/lib/e2e-utils/index.ts

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @JamBalaya56562 - I've reviewed your changes - here's some feedback:

• Consider adding a spellchecking lint rule or CI step for comments and string literals to catch typos like ‘immedately’ and ‘continously’ automatically.
• Make sure all inline snapshots and tests referencing the old typos (e.g., ‘.leve1.level2.child’) are updated to match the corrected strings.
• Given the large volume of non-functional changes, consider splitting typo fixes into smaller, grouped commits or PRs to simplify review and rollback if necessary.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- Consider adding a spellchecking lint rule or CI step for comments and string literals to catch typos like ‘immedately’ and ‘continously’ automatically.
- Make sure all inline snapshots and tests referencing the old typos (e.g., ‘.leve1.level2.child’) are updated to match the corrected strings.
- Given the large volume of non-functional changes, consider splitting typo fixes into smaller, grouped commits or PRs to simplify review and rollback if necessary.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}