cleanup

[planetabhi]

Summary by CodeRabbit

• Chores
  • Updated UI dependencies to latest versions for consistency and compatibility:
    • @new-ui/colors to ^2.0.2
    • @new-ui/effects to ^0.1.6
    • @new-ui/reset to ^0.1.0
    • @new-ui/spacings to ^0.1.6
    • @new-ui/typography to ^0.1.9
  • No functional changes expected; improvements are limited to upstream refinements and maintenance updates.

[coderabbitai]

Walkthrough

Version bumps for several @new-ui dependencies in package.json; no code or API changes.

Changes

Cohort / File(s)	Summary
Dependency updates package.json	Bumped versions: @new-ui/colors ^2.0.1 → ^2.0.2, @new-ui/effects ^0.1.5 → ^0.1.6, @new-ui/reset ^0.0.9 → ^0.1.0, @new-ui/spacings ^0.1.5 → ^0.1.6, @new-ui/typography ^0.1.8 → ^0.1.9

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I nibbled through the version vines,
Tiny bumps on dependency lines.
Colors, spacing, type aligned—
Effects reset, all neatly signed.
Hop hop, ship it—clean and fine! 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title "cleanup" is overly generic and does not clearly convey the primary change in this PR; the raw_summary shows this PR specifically bumps several @new-ui dependency versions (colors, effects, reset, spacings, typography). Because the title uses a vague term rather than describing the dependency updates, the check is inconclusive under the provided rules.	Please rename the PR to a concise, descriptive title that reflects the dependency updates (for example: "chore(deps): bump @new-ui packages to patch versions" or "chore(deps): bump @new-ui/colors, effects, reset, spacings, typography"), and add a short body listing the exact version changes; after that, re-run the pre-merge checks so this can be reassessed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd38179 and 44a4b98.

⛔ Files ignored due to path filters (3)

• bun.lock is excluded by !**/*.lock
• dist/index.css is excluded by !**/dist/**
• dist/index.css.map is excluded by !**/dist/**, !**/*.map

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

49-53: Pre-1.0 bumps can be breaking — verify lockfile, peerDeps/engines, and run a smoke build

File: package.json (lines 49–53)

• Lockfile: verification script found no lockfile (no package-lock.json / yarn.lock / pnpm-lock.yaml). Add/update and commit a lockfile so installs resolve to intended versions.
• Peer deps / engines: npm registry query returned only the published version for each package (colors 2.0.2, effects 0.1.6, reset 0.1.0, spacings 0.1.6, typography 0.1.9) — the script output did not show peerDependencies or engines fields; confirm upstream manifests locally if you expect constraints.
• Smoke build: build failed in the verification environment (sh: 1: parcel: not found). Run a smoke build in an environment with devDependencies installed (npm ci / yarn install) or in CI to confirm there are no import/token regressions.

Optional: consider using tilde ranges (~0.x) for 0.x packages to reduce accidental breaking minor updates.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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