Skip to content

💄 Format package.json keywords arrays#175

Merged
taras merged 3 commits intomainfrom
fix/package-json-formatting
Mar 2, 2026
Merged

💄 Format package.json keywords arrays#175
taras merged 3 commits intomainfrom
fix/package-json-formatting

Conversation

@taras
Copy link
Copy Markdown
Member

@taras taras commented Mar 2, 2026

Motivation

The keywords arrays added in commit 9a40478 were formatted as single-line arrays, but Biome's formatting rules require arrays with 4+ items to be expanded to multi-line format.

This fixes the CI formatting check failures.

Changes

Expands keywords arrays in 10 package.json files from:

"keywords": ["effection", "effectionx", "interop", "promise", "then", "chain"],

To:

"keywords": [
  "effection",
  "effectionx",
  "interop",
  "promise",
  "then",
  "chain"
],

Files changed

  • chain/package.json
  • context-api/package.json
  • converge/package.json
  • process/package.json
  • raf/package.json
  • scope-eval/package.json
  • signals/package.json
  • task-buffer/package.json
  • watch/package.json
  • worker/package.json

Summary by CodeRabbit

Release Notes

  • Chores
    • Reformatted package manifest metadata across multiple modules for improved readability. No functional or behavioral changes.

Expand keywords arrays to multi-line format per Biome formatting rules.
Fixes CI formatting check failures from the keywords addition.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 2, 2026

Warning

Rate limit exceeded

@taras has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 0 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 5bfa5f0 and 8b2af91.

📒 Files selected for processing (2)
  • .policies/package-json-metadata.md
  • www/tailwind/main.css
📝 Walkthrough

Walkthrough

The PR reformats the keywords field across 10 package.json files in different packages from single-line arrays to multi-line arrays. All keyword values remain identical with no semantic or functional changes.

Changes

Cohort / File(s) Summary
Package manifest formatting
chain/package.json, context-api/package.json, converge/package.json, process/package.json, raf/package.json, scope-eval/package.json, signals/package.json, task-buffer/package.json, watch/package.json, worker/package.json
Reformatted the keywords field from compact single-line arrays to multi-line arrays with identical string elements and no semantic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the primary change: formatting package.json keywords arrays to comply with Biome formatting rules.
Description check ✅ Passed The description follows the template with clear Motivation and Approach sections, explaining the CI formatting issue and the multi-line array solution.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Policy Compliance ✅ Passed All 10 packages have valid description fields complying with the Package.json Metadata Policy. Version Bump Policy does not apply as PR contains only formatting changes, not source code changes.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/package-json-formatting

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented Mar 2, 2026

Open in StackBlitz

@effectionx/chain

npm i https://pkg.pr.new/@effectionx/chain@175

@effectionx/context-api

npm i https://pkg.pr.new/@effectionx/context-api@175

@effectionx/converge

npm i https://pkg.pr.new/@effectionx/converge@175

@effectionx/process

npm i https://pkg.pr.new/@effectionx/process@175

@effectionx/raf

npm i https://pkg.pr.new/@effectionx/raf@175

@effectionx/scope-eval

npm i https://pkg.pr.new/@effectionx/scope-eval@175

@effectionx/signals

npm i https://pkg.pr.new/@effectionx/signals@175

@effectionx/task-buffer

npm i https://pkg.pr.new/@effectionx/task-buffer@175

@effectionx/watch

npm i https://pkg.pr.new/@effectionx/watch@175

@effectionx/worker

npm i https://pkg.pr.new/@effectionx/worker@175

commit: c1e390a

taras added 2 commits March 2, 2026 17:00
This file was accidentally included in commit 9a40478 and contains CSS
parsing errors that break the Biome lint check.
Keywords are now required for website categorization and llms.txt grouping.
Defines 8 approved category keywords: testing, io, process, streams,
concurrency, reactivity, interop, platform.
@taras taras merged commit 7727006 into main Mar 2, 2026
6 checks passed
@taras taras deleted the fix/package-json-formatting branch March 2, 2026 22:16
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