[draft] daily release#343
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThis update includes dependency version adjustments across multiple packages, notably downgrading React to 19.0.0 in several places. Documentation improvements clarify the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant EditorApp
participant LucideReact
participant SitemapGen
User->>EditorApp: Requests landing page
EditorApp->>LucideReact: Renders icons for features
EditorApp->>SitemapGen: Generates sitemap.xml for public pages
SitemapGen-->>EditorApp: Returns sitemap data
EditorApp-->>User: Serves landing page with updated icons and sitemap
Possibly related PRs
Poem
Note ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. Note ⚡️ Faster reviews with cachingCodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure ✨ Finishing Touches
🧪 Generate Unit Tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (4)
CONTRIBUTING.md (2)
8-8: Remove inline comment from code block for clarity
Comments like# clone the repoinside the fenced code block can be moved to prose above the block (e.g., as a list item) so the code snippet focuses purely on the commands.
11-14: Clarify Node.js version and pre-requisites
The newnvm useandcorepack enable pnpmsteps are essential for environment consistency. To avoid ambiguity:
- Reference a
.nvmrcfile or replacenvm usewithnvm use [version]ornvm use --lts.- Note that
nvmmust be installed (e.g., link to its installation guide).- Optionally mention that Corepack is built into Node.js ≥ 16.9.0, so no extra install is needed.
AGENTS.md (1)
85-87: Use hyphens for compound modifiers in docs. To improve readability and correctness, hyphenate “page-specific” and capitalize sentence starts. For example:- - `(www)` contains the landing page, seo-purpose static pages. when to add new webpages, this is the root directory. - - `sitemap.ts` contains the sitemap.xml generator. this contains the sitemap for the public pages, usually under `(www)` directory. - - `/www` contains the landing page specific components. + - `(www)` contains the landing-page–specific, SEO-purpose static pages. When adding new webpages, this is the root directory. + - `sitemap.ts` contains the sitemap.xml generator for public pages under the `(www)` directory. + - `/www` contains the landing-page–specific components.🧰 Tools
🪛 LanguageTool
[uncategorized] ~87-~87: When ‘page-specific’ is used as a modifier, it is usually spelled with a hyphen.
Context: ...ectory. -/wwwcontains the landing page specific components. -/componentscontains ...(SPECIFIC_HYPHEN)
editor/app/(www)/(west)/west/page.tsx (1)
25-25: Consolidate lucide-react imports
TheChartLineIconimport on its own line can be merged with the existinglucide-reactimport at line 6 to reduce fragmentation.Apply:
-import { ArrowRight, GiftIcon, Link2, Percent, Star } from "lucide-react"; -import { ChartLineIcon } from "lucide-react"; +import { ArrowRight, GiftIcon, Link2, Percent, Star, ChartLineIcon } from "lucide-react";
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (28)
AGENTS.md(1 hunks)CONTRIBUTING.md(1 hunks)apps/backgrounds/package.json(1 hunks)apps/blog/package.json(1 hunks)apps/docs/package.json(1 hunks)apps/viewer/app/globals.css(1 hunks)apps/viewer/app/page.tsx(1 hunks)apps/viewer/package.json(1 hunks)apps/viewer/postcss.config.mjs(1 hunks)apps/viewer/scaffolds/pdf-page-flip/index.tsx(2 hunks)apps/viewer/tailwind.config.ts(0 hunks)desktop/package.json(1 hunks)editor/app/(www)/(forms)/forms/_sections/features.tsx(2 hunks)editor/app/(www)/(west)/west/page.tsx(2 hunks)editor/package.json(4 hunks)editor/scaffolds/editor/init.ts(2 hunks)editor/www/icons/index.ts(0 hunks)editor/www/icons/mdi-account-tree.tsx(0 hunks)editor/www/icons/mdi-api.tsx(0 hunks)editor/www/icons/mdi-dashboard-customize.tsx(0 hunks)editor/www/icons/mdi-smart-toy.tsx(0 hunks)editor/www/icons/unicons-analysis.tsx(0 hunks)editor/www/icons/unicons-visual-studio.tsx(0 hunks)packages/grida-canvas-pixelgrid/package.json(1 hunks)packages/grida-canvas-react-timeline/package.json(1 hunks)packages/grida-canvas-ruler/package.json(1 hunks)packages/grida-canvas-transparency-grid/package.json(1 hunks)packages/react-p-queue/package.json(1 hunks)
💤 Files with no reviewable changes (8)
- apps/viewer/tailwind.config.ts
- editor/www/icons/mdi-account-tree.tsx
- editor/www/icons/mdi-dashboard-customize.tsx
- editor/www/icons/unicons-visual-studio.tsx
- editor/www/icons/mdi-api.tsx
- editor/www/icons/unicons-analysis.tsx
- editor/www/icons/mdi-smart-toy.tsx
- editor/www/icons/index.ts
🧰 Additional context used
🪛 LanguageTool
AGENTS.md
[uncategorized] ~87-~87: When ‘page-specific’ is used as a modifier, it is usually spelled with a hyphen.
Context: ...ectory. - /www contains the landing page specific components. - /components contains ...
(SPECIFIC_HYPHEN)
🔇 Additional comments (28)
desktop/package.json (1)
27-28:Details
❓ Verification inconclusive
Center React versions at 19.0.0 for desktop
Downgradingreactandreact-domto 19.0.0 aligns with other workspaces. Verify there are no lingering references to 19.1.0 and that v19.0.0 supports all required features.Run this script to confirm:
🏁 Script executed:
#!/bin/bash # Check for any package.json still pinning react or react-dom to 19.1.0 rg -l '"react(-dom)?"\s*:\s*"19\.1\.0"' -g '*.json'Length of output: 53
Confirm React version alignment
The grep scan found no remaining
19.1.0pins in anypackage.json, so desktop is now consistent at19.0.0.• No JSON files reference
"react"or"react-dom"at19.1.0.
• Please manually verify that all React APIs and features in use are supported in v19.0.0.packages/grida-canvas-react-timeline/package.json (1)
7-7: React devDependency pinned to 19.0.0
This matches the workspace downgrade and keeps consistency.packages/grida-canvas-ruler/package.json (1)
42-42: Align React devDependency version
Downgraded React to 19.0.0 to maintain parity across packages.packages/grida-canvas-pixelgrid/package.json (1)
43-43: React devDependency updated to 19.0.0
Consistent version bump across canvas packages.packages/react-p-queue/package.json (1)
39-39: Standardize React devDependency to 19.0.0
Downgrading React aligns this library with the monorepo's baseline.packages/grida-canvas-transparency-grid/package.json (1)
49-49:Details
✅ Verification successful
Align React version in devDependencies. The downgrade to
"19.0.0"ensures consistency with the monorepo’s React versions. Please verify that no other package.json file still references a different React version.You can run this script to confirm:
🏁 Script executed:
#!/bin/bash # Verify all React versions across package.json files are 19.0.0 rg -H '"react": "([^"]+)"' -g '**/package.json'Length of output: 979
🏁 Script executed:
#!/bin/bash set -e echo "=== packages/grida-canvas-transparency-grid/package.json ===" rg -n '"react":' -B2 -A2 packages/grida-canvas-transparency-grid/package.json echo echo "=== packages/grida-canvas-ruler/package.json ===" rg -n '"react":' -B2 -A2 packages/grida-canvas-ruler/package.jsonLength of output: 987
Consistency check passed: React versions aligned across the monorepo. All
package.jsonfiles now pin React to"19.0.0"in Dev/Dependencies, and peerDependencies retain the compatible range^18.0.0 || ^19.0.0. No remaining mismatches detected.apps/backgrounds/package.json (2)
19-20: Review React and React-DOM version specifiers. Switching to the exact"19.0.0"pins the dependencies and prevents minor updates. Confirm this aligns with the project’s versioning strategy, or consider using a caret (^19.0.0) if you want minor upgrades allowed.
27-27: Add @tailwindcss/postcss plugin. Introducing@tailwindcss/postcss@^4is required for Tailwind CSS v4 compatibility. Ensure your PostCSS configuration (e.g.,postcss.config.js) is updated to include this plugin.apps/blog/package.json (2)
20-22: Upgrade MDX, clsx, and prism-react-renderer. Bumping@mdx-js/reactto^3.1.0,clsxto^2.1.1, andprism-react-rendererto^2.4.1brings in minor enhancements and fixes. Verify compatibility by running a local build and smoke-testing content rendering.
23-24: Pin React and React-DOM to 19.0.0. Locking to exact versions disallows minor upgrades. Validate this choice against the monorepo’s dependency policy and ensure no version drift exists elsewhere.apps/viewer/package.json (3)
14-14: Upgrade Lucide React icons. Movinglucide-reactfrom^0.367.0to^0.511.0may include breaking changes or renamed exports. Search for affected icon imports in your components and update them accordingly.
17-18: Pin React and React-DOM to 19.0.0. Downgrading from19.1.0to19.0.0aligns this app with the monorepo’s React footprint. Confirm that exact-version pinning matches your release management guidelines.
23-24: Update ESLint, PostCSS, and Tailwind CSS. Adding@eslint/eslintrc@^3,@tailwindcss/postcss@^4, upgradingeslint-config-nextto15.3.2, and bumpingtailwindcssto^4are needed for Next.js 15 and Tailwind v4 compatibility. Ensure your ESLint config andpostcss.config.js/tailwind.config.jsreflect these updates and that lint/build pipelines pass without errors.Also applies to: 29-29, 31-31
editor/scaffolds/editor/init.ts (2)
717-719: Rename from "campaign" to "form" improves clarity and consistency.This change makes the sidebar folder labeling more intuitive by aligning it with the actual content it contains.
750-758: Good addition of Settings menu item.Adding a dedicated Settings menu item under the Form folder provides users with a clear access point for form configuration options.
apps/docs/package.json (2)
21-25: Docusaurus packages pinned to exact version.Using exact versions (removing carets) for Docusaurus packages ensures consistent behavior across environments.
26-28: Support packages updated to latest compatible versions.These dependency updates ensure compatibility with the other package changes.
apps/viewer/app/page.tsx (1)
16-16: CSS class updated for Tailwind v4 compatibility.Changed
focus-visible:outline-nonetofocus-visible:outline-hiddento align with Tailwind CSS v4 syntax.apps/viewer/postcss.config.mjs (1)
4-4:Details
❓ Verification inconclusive
Updated Tailwind CSS plugin for v4 compatibility.
Changed from
tailwindcssto@tailwindcss/postcssto use the correct plugin identifier for Tailwind CSS v4.
🏁 Script executed:
#!/bin/bash # Verify Tailwind CSS version and related configuration echo "Checking Tailwind CSS version:" grep -r "tailwindcss" --include="package.json" apps/viewer | grep -v "node_modules" echo -e "\nChecking for other PostCSS config files that might need updating:" fd -t f "postcss.config.{js,mjs,cjs,ts}" -E "**/node_modules/**"Length of output: 806
🏁 Script executed:
#!/bin/bash # Find all PostCSS config files in the repo, excluding node_modules fd --glob "postcss.config.js" \ --glob "postcss.config.cjs" \ --glob "postcss.config.mjs" \ --glob "postcss.config.ts" \ -E "node_modules"Length of output: 357
🏁 Script executed:
#!/bin/bash # Locate all PostCSS configuration files in the repository, excluding node_modules find . -type f \( \ -name 'postcss.config.js' -o \ -name 'postcss.config.cjs' -o \ -name 'postcss.config.mjs' -o \ -name 'postcss.config.ts' \ \) -not -path "./node_modules/*"Length of output: 295
🏁 Script executed:
#!/bin/bash # Check plugin identifiers in other PostCSS config files grep -Hn -E "'(tailwindcss|@tailwindcss/postcss)'" ./.legacy/editor/postcss.config.js ./apps/backgrounds/postcss.config.mjs ./editor/postcss.config.mjs || trueLength of output: 166
🏁 Script executed:
#!/bin/bash # Display contents of other PostCSS config files to verify plugin usage for file in ./.legacy/editor/postcss.config.js ./apps/backgrounds/postcss.config.mjs ./editor/postcss.config.mjs; do echo "=== $file ===" sed -n '1,200p' "$file" echo doneLength of output: 1038
🏁 Script executed:
#!/bin/bash # Display the contents of apps/viewer/postcss.config.mjs to verify plugin syntax sed -n '1,200p' ./apps/viewer/postcss.config.mjsLength of output: 194
PostCSS Tailwind Plugin Updated for v4—Please Confirm Legacy Config
- apps/viewer/postcss.config.mjs now correctly uses
@tailwindcss/postcss.- Verified apps/backgrounds/postcss.config.mjs and editor/postcss.config.mjs are also on
@tailwindcss/postcss..legacy/editor/postcss.config.jsstill references the oldtailwindcsskey.
• If that project is migrating to Tailwind v4, update its plugin identifier to@tailwindcss/postcss.
• Otherwise, no action needed there.No further changes required in apps/viewer.
editor/app/(www)/(west)/west/page.tsx (1)
185-185: Icon replacement appears correct
Using<ChartLineIcon />for real-time analytics now aligns with the newlucide-reactlibrary and removes the localAnalysisIcon.apps/viewer/scaffolds/pdf-page-flip/index.tsx (2)
47-47: Approve Tailwind border-radius adjustment
Changingroundedtorounded-smfits the Tailwind v4 styling updates.
367-367: Approve input border-radius adjustment
Updating the input fromroundedtorounded-smmaintains consistency with the new base styles.editor/app/(www)/(forms)/forms/_sections/features.tsx (2)
2-8: Approve icon import migration
Switching from the local@/www/iconsmodule tolucide-reactcentralizes icon assets and aligns with other parts of the codebase.
19-19: Icon usage updated to lucide-react
All feature cards now correctly use the external icons withclassName="size-6".Also applies to: 27-27, 33-33, 40-40, 47-47, 54-54
editor/package.json (1)
48-48: Approve dependency version updates
Bumped@mdx-js/reactto ^3.1.0,lucide-reactto ^0.511.0,prism-react-rendererto ^2.4.1, andsvg-pathdatato ^7.2.0 to stay consistent with other packages.Also applies to: 156-156, 172-172, 202-202
apps/viewer/app/globals.css (3)
1-1: Approve Tailwind import syntax
Replacing the@tailwinddirectives with@import 'tailwindcss';is correct for the new PostCSS plugin configuration.
3-6: Approve custom theme properties
Defining--color-backgroundand--color-foregroundunder@themeensures consistent theming across light/dark modes.
16-24: Approve base layer compatibility styles
Adding defaultborder-colorrules maintains visual consistency after the Tailwind v4 update.
| "react": "19.0.0", | ||
| "react-dom": "19.0.0" |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
React downgraded to exact version 19.0.0.
This aligns with the repo-wide React version standardization mentioned in the PR summary.
🏁 Script executed:
#!/bin/bash
# Check for React version consistency across the repository
echo "Checking React versions across the repository:"
fd -t f "package.json" -E "**/node_modules/**" -E "**/.next/**" -x grep -l "\"react\":" {} \; | xargs grep -h "\"react\": " | sort | uniq -cLength of output: 369
🏁 Script executed:
#!/bin/bash
echo "Listing package.json files with React version '^18.0.0 || ^19.0.0':"
fd -t f "package.json" -E "**/node_modules/**" -E "**/.next/**" -x grep -l '"react": "\^18\.0\.0 \|\| \^19\.0\.0"' {} \;Length of output: 1270
Inconsistent React version specifiers across repository
The update in apps/docs/package.json to "react": "19.0.0" is correct, but our scan shows many other package.json files still use the range specifier ^18.0.0 || ^19.0.0. For full repo-wide standardization, please update all of them to the exact "19.0.0".
Files needing update (examples):
- packages/grida-canvas-schema/package.json
- packages/grida-canvas-io/package.json
- packages/grida-canvas-react-timeline/package.json
- …and 20+ more (see script output)
• Run:
grep -R '"react": "\^18\.0\.0 \|\| \^19\.0\.0"' -n .and replace each occurrence with:
- "react": "^18.0.0 || ^19.0.0",
+ "react": "19.0.0",🤖 Prompt for AI Agents
In apps/docs/package.json at lines 29 to 30, the React version is set to the
exact "19.0.0" which is correct. However, to ensure consistency across the
repository, locate all other package.json files that specify React with the
range "^18.0.0 || ^19.0.0" and update those entries to the exact version
"19.0.0". Use the provided grep command to find all occurrences and replace them
accordingly to standardize React versioning repo-wide.
1 participant
Summary by CodeRabbit
Documentation
New Features
Bug Fixes
Refactor
Chores