Skip to content

chore: fix typos in next package - #24

Closed
JamBalaya56562 wants to merge 1 commit into
canaryfrom
next-package
Closed

JamBalaya56562 wants to merge 1 commit into
canaryfrom
next-package

Conversation

@JamBalaya56562

@JamBalaya56562 JamBalaya56562 commented Aug 10, 2025 •

Copy link
Copy Markdown
Owner

Summary by Sourcery

Correct typos in comments, documentation, and identifier names across the Next.js codebase.

Documentation:

  • Fix typo in next-devtools README styling section

Chores:

  • Correct misspellings in code comments and improve grammar across multiple modules
  • Rename misnamed variables and parameters for clarity (e.g., varialbeRule to variableRule, _lineNumer to _lineNumber)
  • Fix spelling errors in source code comments and documentation (e.g., prioritize, initiated, delimiter)

@sourcery-ai

sourcery-ai Bot commented Aug 10, 2025 •

Copy link
Copy Markdown

Reviewer's Guide

This PR applies widespread spelling corrections across the Next.js codebase, fixing typos in comments, documentation strings, README files, and renaming a few misnamed identifiers for clarity and consistency.

Class diagram for corrected identifier in postcss-next-font.ts

classDiagram
    class postcssNextFontPlugin {
        +variableRule: Rule
        +variableRule.nodes: Declaration[]
    }
Loading

Class diagram for corrected identifier in parseScss.ts

classDiagram
    class getScssError {
        +_lineNumber: string
        +lineNumber: number
    }
Loading

File-Level Changes

Change Details Files
Correct spelling errors in comments and documentation
  • Fix various comment typos (e.g., priortize→prioritize, simlar→similar, unncessarily→unnecessarily)
  • Update documentation and error messages (e.g., addtional→additional, superceded→superseded, direcly→directly)
packages/next/src/client/components/segment-cache-impl/scheduler.ts
packages/next/src/client/components/router-reducer/ppr-navigations.ts
packages/next/src/client/link.tsx
packages/next/src/server/lib/source-maps.ts
packages/next/src/server/typescript/rules/config.ts
packages/next/src/server/use-cache/use-cache-wrapper.ts
packages/next/src/shared/lib/hash.ts
packages/next/src/trace/trace-uploader.ts
packages/next/src/build/analysis/extract-const-value.ts
packages/next/src/build/normalize-catchall-routes.ts
packages/next/src/build/swc/index.ts
packages/next/src/build/webpack-config.ts
packages/next/src/build/webpack/plugins/flight-manifest-plugin.ts
packages/next/src/build/webpack/plugins/middleware-plugin.ts
packages/next/src/cli/next-info.ts
packages/next/src/client/app-build-id.ts
packages/next/src/client/app-index.tsx
packages/next/src/client/components/router-reducer/prefetch-cache-utils.ts
packages/next/src/client/components/router-reducer/refetch-inactive-parallel-segments.ts
packages/next/src/client/components/segment-cache-impl/cache.ts
packages/next/src/lib/metadata/types/extra-types.ts
packages/next/src/lib/metadata/types/metadata-interface.ts
packages/next/src/next-devtools/README.md
packages/next/src/next-devtools/dev-overlay/shared.ts
packages/next/src/next-devtools/server/launch-editor.ts
packages/next/src/server/after/after-context.ts
packages/next/src/server/app-render/collect-segment-data.tsx
packages/next/src/server/app-render/dynamic-rendering.ts
packages/next/src/server/next-server.ts
packages/next/src/server/next.ts
packages/next/src/shared/lib/turbopack/utils.ts
Rename misnamed internal identifiers
  • Rename varialbeRule to variableRule in CSS font loader
  • Fix parameter _lineNumer to _lineNumber in SCSS error parser
  • Correct callback parameter entryEonfig to entryConfig in TypeScript rules
packages/next/src/build/webpack/loaders/next-font-loader/postcss-next-font.ts
packages/next/src/build/webpack/plugins/wellknown-errors-plugin/parseScss.ts
packages/next/src/server/typescript/rules/config.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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey @JamBalaya56562 - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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.

1 participant