Skip to content

fix(core): correct 'occured' typo to 'occurred' in error messages#35852

Merged
FrozenPandaz merged 4 commits into
nrwl:masterfrom
DucMinhNe:fix/occured-typo-nx-errors
Jun 3, 2026
Merged

fix(core): correct 'occured' typo to 'occurred' in error messages#35852
FrozenPandaz merged 4 commits into
nrwl:masterfrom
DucMinhNe:fix/occured-typo-nx-errors

Conversation

@DucMinhNe

Copy link
Copy Markdown
Contributor

Current Behavior

Three error/diagnostic messages in the nx package misspell "occurred" as "occured":

  • packages/nx/src/plugins/js/lock-file/lock-file.tstitle: 'An error occured while creating pruned lockfile' (shown to users on lockfile pruning failure)
  • packages/nx/src/command-line/graph/graph.ts"... occured while processing the project graph. Showing partial graph." (console output)
  • packages/nx/src/project-graph/error-types.ts — doc comment "... errors which occured."

Expected Behavior

The word is spelled "occurred" in all three places.

Related Issue(s)

N/A — spelling-only fix, no behavior change.

@DucMinhNe DucMinhNe requested a review from a team as a code owner June 2, 2026 12:43
@DucMinhNe DucMinhNe requested a review from leosvelperez June 2, 2026 12:43
@netlify

netlify Bot commented Jun 2, 2026

Copy link
Copy Markdown

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit e0ff257

@netlify

netlify Bot commented Jun 2, 2026

Copy link
Copy Markdown

👷 Deploy request for nx-dev pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit e0ff257

@nx-cloud

nx-cloud Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

View your CI Pipeline Execution ↗ for commit e0ff257

Command Status Duration Result
nx affected --targets=lint,test,build,e2e,e2e-c... ✅ Succeeded 18m 45s View ↗
nx run-many -t check-imports check-lock-files c... ✅ Succeeded 3s View ↗
nx-cloud record -- pnpm nx-cloud conformance:check ✅ Succeeded 16s View ↗
nx build workspace-plugin ✅ Succeeded <1s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded 19s View ↗
nx-cloud record -- nx format:check ✅ Succeeded 5s View ↗

☁️ Nx Cloud last updated this comment at 2026-06-03 15:26:28 UTC

@FrozenPandaz

Copy link
Copy Markdown
Contributor

Thank you for your contribution! LGTM 🎉

nx-cloud[bot]

This comment was marked as outdated.

@nx-cloud nx-cloud Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nx Cloud has identified a flaky task in your failed CI:

Since the failure was identified as flaky, the solution is to rerun CI. Because this branch comes from a fork, it is not possible for us to push directly, but you can rerun by pushing an empty commit:

git commit --allow-empty -m "chore: trigger rerun"
git push

Nx Cloud View detailed reasoning in Nx Cloud ↗


🎓 Learn more about Self-Healing CI on nx.dev

@FrozenPandaz FrozenPandaz merged commit c0b8c34 into nrwl:master Jun 3, 2026
18 of 19 checks passed
vrxj81 pushed a commit to vrxj81/nx that referenced this pull request Jun 7, 2026
…wl#35852)

## Current Behavior

Three error/diagnostic messages in the `nx` package misspell "occurred"
as "occured":

- `packages/nx/src/plugins/js/lock-file/lock-file.ts` — `title: 'An
error occured while creating pruned lockfile'` (shown to users on
lockfile pruning failure)
- `packages/nx/src/command-line/graph/graph.ts` — `"... occured while
processing the project graph. Showing partial graph."` (console output)
- `packages/nx/src/project-graph/error-types.ts` — doc comment `"...
errors which occured."`

## Expected Behavior

The word is spelled "occurred" in all three places.

## Related Issue(s)

N/A — spelling-only fix, no behavior change.
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.

2 participants