Chore/20250723 by SvenVw · Pull Request #195 · nmi-agro/fdm

SvenVw · 2025-07-23T07:34:08Z

Summary by CodeRabbit

Chores
- Upgraded pnpm package manager to version 10.13.1 across all projects and workflows.
- Updated various dependencies in multiple package files, including mapbox-gl-geocoder, react-router, Sentry, flatgeobuf, framer-motion, posthog, proj4, react-day-picker, react-hook-form, sonner, zod, decimal.js, @types/node, @electric-sql/pglite, lucide-react, typedoc-plugin-markdown, @biomejs/biome, turbo, and more.
- Refreshed dependency versions in the workspace configuration for improved compatibility and stability.

changeset-bot · 2025-07-23T07:34:12Z

⚠️ No Changeset found

Latest commit: 264f4de

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

coderabbitai · 2025-07-23T07:34:16Z

Walkthrough

This update upgrades the pnpm package manager version from 10.12.4 to 10.13.1 across all relevant GitHub Actions workflows and package.json files in the repository. Several dependencies in various package.json files and the pnpm-workspace.yaml catalog are also updated to newer versions, with no changes to scripts, exports, or control flow.

Changes

Files/Paths	Change Summary
.github/workflows/deploy-docs-test.yml .github/workflows/deploy-docs.yml .github/workflows/release.yml .github/workflows/tests.yml	Updated pnpm version from 10.12.4 to 10.13.1 in all workflow steps.
fdm-app/package.json	Updated multiple dependencies and devDependencies; removed @types/proj4; bumped pnpm version.
fdm-calculator/package.json	Updated decimal.js version and bumped pnpm version.
fdm-core/package.json	Updated @types/node, @electric-sql/pglite, and pnpm versions.
fdm-data/package.json	Updated pnpm version only.
fdm-docs/package.json	Updated lucide-react, typedoc-plugin-markdown, and pnpm versions.
package.json	Updated @biomejs/biome, turbo, and pnpm versions.
pnpm-workspace.yaml	Updated catalog dependency versions and reordered some entries.

Estimated code review effort

1 (~7 minutes)

Possibly related PRs

Update pnpm to v9.15.4 and refactor package dependencies #47: Updates pnpm version in workflows and package manager fields, but targets a different pnpm version.
Chore/20250619 #174: Bumps pnpm version in similar files, representing a previous increment in the version update sequence.
Chore/20250528 #147: Another pnpm version bump across workflows and package manager fields, part of the ongoing upgrade pattern.

Suggested labels

fdm-app, fdm-core, fdm-data, fdm-calculator, fdm-docs

Poem

Up hops the rabbit, with pnpm in tow,
Upgrading the versions, in files they now glow.
Dependencies refreshed, the workspace anew,
Workflows aligned, the updates are true.
With a twitch of the nose and a satisfied grin,
The code hops ahead—let the builds begin!
🐇✨

✨ Finishing Touches

🧪 Generate unit tests

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch chore/20250723

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai generate unit tests to generate unit tests for this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

codecov · 2025-07-23T07:34:41Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.55%. Comparing base (b31d18c) to head (264f4de).
Report is 9 commits behind head on development.

Additional details and impacted files

@@             Coverage Diff              @@
##           development     #195   +/-   ##
============================================
  Coverage        93.55%   93.55%           
============================================
  Files               74       74           
  Lines             9043     9043           
  Branches          1141     1141           
============================================
  Hits              8460     8460           
  Misses             581      581           
  Partials             2        2

Flag	Coverage Δ
fdm-calculator	`94.86% <ø> (ø)`
fdm-core	`93.19% <ø> (ø)`
fdm-data	`94.21% <ø> (ø)`

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

coderabbitai

Actionable comments posted: 1

🧹 Nitpick comments (2)

fdm-app/package.json (2)

32-35: Duplicated workspace packages inflate lockfile
@svenvw/fdm-{calculator,core,data} are declared in both dependencies and devDependencies. This forces pnpm to write two virtual links for the same workspace package and lengthens install time. Removing them from devDependencies keeps runtime behaviour unchanged.

Also applies to: 85-87

107-107: Remember to update local tooling after changing packageManager
Bumping to pnpm@10.13.1 is fine, but advise contributors to run corepack prepare pnpm@10.13.1 --activate locally to avoid lockfile churn.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b31d18c and 264f4de.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (11)

.github/workflows/deploy-docs-test.yml (1 hunks)
.github/workflows/deploy-docs.yml (1 hunks)
.github/workflows/release.yml (1 hunks)
.github/workflows/tests.yml (3 hunks)
fdm-app/package.json (2 hunks)
fdm-calculator/package.json (2 hunks)
fdm-core/package.json (3 hunks)
fdm-data/package.json (1 hunks)
fdm-docs/package.json (3 hunks)
package.json (2 hunks)
pnpm-workspace.yaml (1 hunks)

🧠 Learnings (9)

📓 Common learnings

Learnt from: SvenVw
PR: SvenVw/fdm#147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax `"typescript": "catalog:"` is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: SvenVw/fdm#147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax `"typescript": "catalog:"` is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

Learnt from: SvenVw
PR: SvenVw/fdm#134
File: fdm-calculator/package.json:44-46
Timestamp: 2025-05-26T09:39:31.123Z
Learning: When analyzing npm package versions in package.json files, the specified versions are often already the latest stable versions, especially in active projects. Always verify with npm registry before suggesting version updates.

.github/workflows/deploy-docs.yml (2)

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

pnpm-workspace.yaml (11)

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: #134
File: fdm-calculator/package.json:44-46
Timestamp: 2025-05-26T09:39:31.123Z
Learning: When analyzing npm package versions in package.json files, the specified versions are often already the latest stable versions, especially in active projects. Always verify with npm registry before suggesting version updates.

Learnt from: SvenVw
PR: #49
File: fdm-data/rollup.config.js:7-17
Timestamp: 2025-01-24T11:46:49.990Z
Learning: When suggesting external dependencies in Rollup configuration, only include packages that are actually listed in the package's dependencies or peerDependencies.

Learnt from: SvenVw
PR: #6
File: fdm-app/vite.config.ts:5-9
Timestamp: 2024-11-25T12:42:32.783Z
Learning: In the fdm-app project, SvenVw is preparing for migration to Remix v3 and may include type declarations or configurations for v3 features in advance, such as in vite.config.ts.

Learnt from: SvenVw
PR: #124
File: fdm-core/src/db/schema-authn.ts:70-76
Timestamp: 2025-04-18T14:20:40.975Z
Learning: The schema defined in fdm-core/src/db/schema-authn.ts follows better-auth's structure and requirements. While the schema is defined in the application code, modifications to it should maintain compatibility with better-auth's expectations.

Learnt from: SvenVw
PR: #124
File: fdm-core/src/db/schema-authn.ts:70-76
Timestamp: 2025-04-18T14:20:40.975Z
Learning: The organization schema in fdm-core/src/db/schema-authn.ts is managed by better-auth, and modifications to field constraints (like making the slug field non-nullable) should maintain compatibility with better-auth's expectations, even if application code assumes non-null values.

Learnt from: SvenVw
PR: #20
File: fdm-app/tsconfig.json:8-9
Timestamp: 2024-12-11T12:09:35.540Z
Learning: In the fdm-app/tsconfig.json file, the include path .react-router/types/**/* refers to a build-time generated directory which is intentionally not included in the repository.

Learnt from: SvenVw
PR: #16
File: fdm-app/package.json:40-40
Timestamp: 2024-12-16T10:48:27.598Z
Learning: In the fdm-app/package.json file, remix-toast and sonner are not duplicate dependencies. remix-toast manages toast generation and handling within the Remix framework, while sonner provides the actual implementation and UI of the toast notifications. They serve different purposes and are intended to be used together in the project.

Learnt from: SvenVw
PR: #95
File: fdm-core/src/catalogues.ts:134-170
Timestamp: 2025-03-06T15:23:48.352Z
Learning: When writing tests for fdm-core, avoid using Vitest's vi mocking utilities and prefer manual JavaScript mocks.

Learnt from: SvenVw
PR: #95
File: fdm-core/src/cultivation.ts:67-73
Timestamp: 2025-03-06T14:58:48.603Z
Learning: When writing unit tests for the fdm project, avoid using Vitest's mocking utilities (vi) as it has caused problems in the past not related to the actual code. Instead, use simple object literals with methods that throw errors to test error handling.

fdm-data/package.json (3)

Learnt from: SvenVw
PR: #134
File: fdm-calculator/package.json:44-46
Timestamp: 2025-05-26T09:39:31.123Z
Learning: When analyzing npm package versions in package.json files, the specified versions are often already the latest stable versions, especially in active projects. Always verify with npm registry before suggesting version updates.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

fdm-calculator/package.json (8)

Learnt from: SvenVw
PR: #67
File: fdm-app/app/routes/farm.create.$b_id_farm.fields.$b_id.tsx:601-610
Timestamp: 2025-01-31T15:05:14.310Z
Learning: The updateField function in fdm-core has optional parameters after fdm and b_id. The TypeScript definitions might show 8 required parameters due to a potential version mismatch.

Learnt from: SvenVw
PR: #134
File: fdm-calculator/package.json:44-46
Timestamp: 2025-05-26T09:39:31.123Z
Learning: When analyzing npm package versions in package.json files, the specified versions are often already the latest stable versions, especially in active projects. Always verify with npm registry before suggesting version updates.

Learnt from: SvenVw
PR: #6
File: fdm-app/vite.config.ts:5-9
Timestamp: 2024-11-25T12:42:32.783Z
Learning: In the fdm-app project, SvenVw is preparing for migration to Remix v3 and may include type declarations or configurations for v3 features in advance, such as in vite.config.ts.

Learnt from: SvenVw
PR: #67
File: fdm-app/app/routes/farm.create.$b_id_farm.fields.$b_id.tsx:601-610
Timestamp: 2025-01-31T15:34:20.850Z
Learning: The updateField function in fdm-core has optional parameters that don't need to be passed as undefined. Only fdm and b_id are required.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

Learnt from: SvenVw
PR: #49
File: fdm-data/rollup.config.js:7-17
Timestamp: 2025-01-24T11:46:49.990Z
Learning: When suggesting external dependencies in Rollup configuration, only include packages that are actually listed in the package's dependencies or peerDependencies.

Learnt from: SvenVw
PR: #16
File: fdm-app/package.json:40-40
Timestamp: 2024-12-16T10:48:27.598Z
Learning: In the fdm-app/package.json file, remix-toast and sonner are not duplicate dependencies. remix-toast manages toast generation and handling within the Remix framework, while sonner provides the actual implementation and UI of the toast notifications. They serve different purposes and are intended to be used together in the project.

fdm-core/package.json (14)

Learnt from: SvenVw
PR: #6
File: fdm-app/vite.config.ts:5-9
Timestamp: 2024-11-25T12:42:32.783Z
Learning: In the fdm-app project, SvenVw is preparing for migration to Remix v3 and may include type declarations or configurations for v3 features in advance, such as in vite.config.ts.

Learnt from: SvenVw
PR: #67
File: fdm-app/app/routes/farm.create.$b_id_farm.fields.$b_id.tsx:601-610
Timestamp: 2025-01-31T15:05:14.310Z
Learning: The updateField function in fdm-core has optional parameters after fdm and b_id. The TypeScript definitions might show 8 required parameters due to a potential version mismatch.

Learnt from: SvenVw
PR: #67
File: fdm-app/app/routes/farm.create.$b_id_farm.fields.$b_id.tsx:601-610
Timestamp: 2025-01-31T15:34:20.850Z
Learning: The updateField function in fdm-core has optional parameters that don't need to be passed as undefined. Only fdm and b_id are required.

Learnt from: SvenVw
PR: #134
File: fdm-calculator/package.json:44-46
Timestamp: 2025-05-26T09:39:31.123Z
Learning: When analyzing npm package versions in package.json files, the specified versions are often already the latest stable versions, especially in active projects. Always verify with npm registry before suggesting version updates.

Learnt from: SvenVw
PR: #88
File: fdm-core/src/cultivation.ts:246-246
Timestamp: 2025-03-04T11:09:08.169Z
Learning: In the FDM codebase, the fdm parameter should be documented as "The FDM instance providing the connection to the database. The instance can be created with {@link createFdmServer}." in JSDoc comments.

Learnt from: SvenVw
PR: #124
File: fdm-core/src/organization.ts:300-339
Timestamp: 2025-04-18T14:51:48.033Z
Learning: The getUsersInOrganization function in fdm-core/src/organization.ts will be updated in commit b17fac1 to include id and email fields, which are necessary for subsequent role updates and user removal operations.

Learnt from: SvenVw
PR: #124
File: fdm-core/src/db/schema-authn.ts:70-76
Timestamp: 2025-04-18T14:20:40.975Z
Learning: The organization schema in fdm-core/src/db/schema-authn.ts is managed by better-auth, and modifications to field constraints (like making the slug field non-nullable) should maintain compatibility with better-auth's expectations, even if application code assumes non-null values.

Learnt from: SvenVw
PR: #124
File: fdm-core/src/organization.ts:300-339
Timestamp: 2025-04-18T14:51:48.033Z
Learning: The getUsersInOrganization function in fdm-core/src/organization.ts needed to include id and email fields for users, which was fixed in commit b17fac1.

Learnt from: SvenVw
PR: #16
File: fdm-app/package.json:40-40
Timestamp: 2024-12-16T10:48:27.598Z
Learning: In the fdm-app/package.json file, remix-toast and sonner are not duplicate dependencies. remix-toast manages toast generation and handling within the Remix framework, while sonner provides the actual implementation and UI of the toast notifications. They serve different purposes and are intended to be used together in the project.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

Learnt from: SvenVw
PR: #49
File: fdm-data/rollup.config.js:7-17
Timestamp: 2025-01-24T11:46:49.990Z
Learning: When suggesting external dependencies in Rollup configuration, only include packages that are actually listed in the package's dependencies or peerDependencies.

Learnt from: SvenVw
PR: #20
File: fdm-app/tsconfig.json:8-9
Timestamp: 2024-12-11T12:09:35.540Z
Learning: In the fdm-app/tsconfig.json file, the include path .react-router/types/**/* refers to a build-time generated directory which is intentionally not included in the repository.

Learnt from: SvenVw
PR: #124
File: fdm-core/src/db/schema-authn.ts:70-76
Timestamp: 2025-04-18T14:20:40.975Z
Learning: The schema defined in fdm-core/src/db/schema-authn.ts follows better-auth's structure and requirements. While the schema is defined in the application code, modifications to it should maintain compatibility with better-auth's expectations.

fdm-app/package.json (18)

Learnt from: SvenVw
PR: #20
File: fdm-app/tsconfig.json:8-9
Timestamp: 2024-12-11T12:09:35.540Z
Learning: In the fdm-app/tsconfig.json file, the include path .react-router/types/**/* refers to a build-time generated directory which is intentionally not included in the repository.

Learnt from: SvenVw
PR: #45
File: fdm-app/app/routes/farm.$b_id_farm.settings._index.tsx:1-1
Timestamp: 2025-01-14T16:06:21.832Z
Learning: In the fdm project, redirect and other routing utilities should be imported from react-router instead of react-router-dom.

Learnt from: SvenVw
PR: #6
File: fdm-app/vite.config.ts:5-9
Timestamp: 2024-11-25T12:42:32.783Z
Learning: In the fdm-app project, SvenVw is preparing for migration to Remix v3 and may include type declarations or configurations for v3 features in advance, such as in vite.config.ts.

Learnt from: SvenVw
PR: #45
File: fdm-app/app/routes/farm.$b_id_farm._index.tsx:1-1
Timestamp: 2025-01-14T16:06:24.294Z
Learning: In the fdm-app codebase, the redirect function should be imported from react-router, not react-router-dom.

Learnt from: SvenVw
PR: #124
File: fdm-app/app/components/custom/farm/farm-title.tsx:3-3
Timestamp: 2025-04-18T13:49:17.029Z
Learning: In the fdm project, NavLink and other routing components can be imported from either "react-router" or "react-router-dom" as react-router-dom is included in react-router.

Learnt from: SvenVw
PR: #16
File: fdm-app/package.json:40-40
Timestamp: 2024-12-16T10:48:27.598Z
Learning: In the fdm-app/package.json file, remix-toast and sonner are not duplicate dependencies. remix-toast manages toast generation and handling within the Remix framework, while sonner provides the actual implementation and UI of the toast notifications. They serve different purposes and are intended to be used together in the project.

Learnt from: SvenVw
PR: #67
File: fdm-app/app/routes/farm.create.$b_id_farm.fields.$b_id.tsx:601-610
Timestamp: 2025-01-31T15:05:14.310Z
Learning: The updateField function in fdm-core has optional parameters after fdm and b_id. The TypeScript definitions might show 8 required parameters due to a potential version mismatch.

Learnt from: SvenVw
PR: #134
File: fdm-calculator/package.json:44-46
Timestamp: 2025-05-26T09:39:31.123Z
Learning: When analyzing npm package versions in package.json files, the specified versions are often already the latest stable versions, especially in active projects. Always verify with npm registry before suggesting version updates.

Learnt from: SvenVw
PR: #124
File: fdm-core/src/organization.ts:300-339
Timestamp: 2025-04-18T14:51:48.033Z
Learning: The getUsersInOrganization function in fdm-core/src/organization.ts will be updated in commit b17fac1 to include id and email fields, which are necessary for subsequent role updates and user removal operations.

Learnt from: SvenVw
PR: #124
File: fdm-core/src/organization.ts:300-339
Timestamp: 2025-04-18T14:51:48.033Z
Learning: The getUsersInOrganization function in fdm-core/src/organization.ts needed to include id and email fields for users, which was fixed in commit b17fac1.

Learnt from: SvenVw
PR: #138
File: fdm-app/app/components/custom/fertilizer-applications/form.tsx:6-6
Timestamp: 2025-05-09T14:41:43.484Z
Learning: The project uses React Router v7 which exports a Form component directly from the "react-router" package, making importing from "@remix-run/react" unnecessary.

Learnt from: SvenVw
PR: #138
File: fdm-app/app/components/custom/fertilizer-applications/form.tsx:6-6
Timestamp: 2025-05-09T14:41:43.484Z
Learning: The project uses React Router v7 which exports a Form component directly from the "react-router" package, not from "@remix-run/react".

Learnt from: SvenVw
PR: #138
File: fdm-app/app/components/custom/combobox.tsx:34-37
Timestamp: 2025-05-09T14:53:44.578Z
Learning: In the context of this React Router v7 project, it's important to follow the pattern of importing only the types (like UseFormReturn) from "react-hook-form" while importing the Form component from "react-router" to avoid naming conflicts.

Learnt from: SvenVw
PR: #138
File: fdm-app/app/components/custom/combobox.tsx:34-37
Timestamp: 2025-05-09T14:58:10.465Z
Learning: When updating React components that use both react-hook-form and React Router v7, it's important to only import types (like UseFormReturn, FieldValues) from react-hook-form to avoid naming conflicts with React Router's Form component. Use import type { ... } from 'react-hook-form' syntax to ensure only types are imported.

Learnt from: SvenVw
PR: #49
File: fdm-data/rollup.config.js:7-17
Timestamp: 2025-01-24T11:46:49.990Z
Learning: When suggesting external dependencies in Rollup configuration, only include packages that are actually listed in the package's dependencies or peerDependencies.

Learnt from: SvenVw
PR: #16
File: fdm-app/app/routes/app.addfarm.$b_id_farm.cultivations.$b_lu_catalogue.fertilizers.tsx:1-1
Timestamp: 2024-12-16T10:56:07.561Z
Learning: The project uses react-router v7, and the data function is exported and used for error handling in loaders and actions.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

fdm-docs/package.json (3)

Learnt from: SvenVw
PR: #134
File: fdm-calculator/package.json:44-46
Timestamp: 2025-05-26T09:39:31.123Z
Learning: When analyzing npm package versions in package.json files, the specified versions are often already the latest stable versions, especially in active projects. Always verify with npm registry before suggesting version updates.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

package.json (4)

Learnt from: SvenVw
PR: #134
File: fdm-calculator/package.json:44-46
Timestamp: 2025-05-26T09:39:31.123Z
Learning: When analyzing npm package versions in package.json files, the specified versions are often already the latest stable versions, especially in active projects. Always verify with npm registry before suggesting version updates.

Learnt from: SvenVw
PR: #6
File: fdm-app/vite.config.ts:5-9
Timestamp: 2024-11-25T12:42:32.783Z
Learning: In the fdm-app project, SvenVw is preparing for migration to Remix v3 and may include type declarations or configurations for v3 features in advance, such as in vite.config.ts.

Learnt from: SvenVw
PR: #147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax "typescript": "catalog:" is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: #49
File: fdm-data/rollup.config.js:7-17
Timestamp: 2025-01-24T11:46:49.990Z
Learning: When suggesting external dependencies in Rollup configuration, only include packages that are actually listed in the package's dependencies or peerDependencies.

🧰 Additional context used

🧠 Learnings (9)

📓 Common learnings

Learnt from: SvenVw
PR: SvenVw/fdm#147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax `"typescript": "catalog:"` is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo.

Learnt from: SvenVw
PR: SvenVw/fdm#147
File: fdm-docs/package.json:39-39
Timestamp: 2025-05-28T07:57:19.217Z
Learning: In pnpm workspaces, the syntax `"typescript": "catalog:"` is valid and correct. It references the version defined in the workspace's catalog section in pnpm-workspace.yaml, allowing consistent dependency versions across packages in a monorepo. The catalog: syntax without a package name is the shorthand for referencing the default catalog.

Learnt from: SvenVw
PR: SvenVw/fdm#134
File: fdm-calculator/package.json:44-46
Timestamp: 2025-05-26T09:39:31.123Z
Learning: When analyzing npm package versions in package.json files, the specified versions are often already the latest stable versions, especially in active projects. Always verify with npm registry before suggesting version updates.