Skip to content

Update system-requirements.md#17581

Merged
mpysiak merged 1 commit intoSylius:2.0from
tomkalon:fix/docs-system-requirements
Dec 17, 2024
Merged

Update system-requirements.md#17581
mpysiak merged 1 commit intoSylius:2.0from
tomkalon:fix/docs-system-requirements

Conversation

@tomkalon
Copy link
Copy Markdown
Contributor

@tomkalon tomkalon commented Dec 17, 2024

Sylius 2.0

Changed system requirements:
NodeJS 18.x || 20.x
to:
NodeJS 20.x || 22.x

error @sylius-ui/admin@2.0.0: The engine "node" is incompatible with this module. Expected version "^20 || ^22". Got "18.20.5"

Summary by CodeRabbit

  • Documentation
    • Updated system requirements to reflect the new Node.js version requirement from ^18 || ^20 to ^20 || ^22.

@tomkalon tomkalon requested review from a team as code owners December 17, 2024 11:13
@probot-autolabeler probot-autolabeler bot added Documentation Documentation related issues and PRs - requests, fixes, proposals. Maintenance CI configurations, READMEs, releases, etc. labels Dec 17, 2024
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Dec 17, 2024

Walkthrough

The documentation for system requirements has been updated to modify the supported Node.js versions. The change reflects an expansion of compatible Node.js versions, removing support for version 18 and adding support for version 22, while maintaining version 20 as a supported option.

Changes

File Change Summary
docs/the-book/installation/system-requirements.md Updated Node.js version requirements from `^18

Poem

🐰 Nodes of code, versions anew,
From eighteen to twenty-two,
Our system's heart beats bright and clear,
Compatibility draws near!
A rabbit's leap through version's gate 🚀


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
docs/the-book/installation/system-requirements.md (1)

10-10: LGTM, but consider adding migration notes

The Node.js version update is technically accurate and aligns with the @sylius-ui/admin@2.0.0 module requirements. However, since this is a breaking change that removes support for Node.js 18, consider adding a note about migration path for existing installations.

Consider adding a note below the requirements table:

| [Node.js](https://nodejs.org/en) `^20 || ^22`                                                                                                                                                                                              |
| Git                                                                                                                                                                                                                                          |

+{% hint style="warning" %}
+**Note:** If you're upgrading from a previous version using Node.js 18, you'll need to upgrade to Node.js 20 or 22 to ensure compatibility with @sylius-ui/admin@2.0.0.
+{% endhint %}

{% hint style="info" %}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 259feb5 and 3c2bb4b.

📒 Files selected for processing (1)
  • docs/the-book/installation/system-requirements.md (1 hunks)

| [Composer](https://getcomposer.org/download/) |
| <p>One of the supported database engines:</p><ul><li>MySQL <code>8.0</code> or higher</li><li>MariaDB <code>10.4.10</code> or higher</li><li>PostgreSQL <code>13.9</code> or higher</li></ul> |
| [Node.js](https://nodejs.org/en) `^18 \|\| ^20` |
| [Node.js](https://nodejs.org/en) `^20 \|\| ^22` |
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codebase verification

Node.js 22 requirement should be removed at this time

The current @sylius-ui/admin package officially supports Node.js 18 and 20, but not Node.js 22. Additionally, Node.js 22 is not yet released (scheduled for April 24, 2024) and won't reach LTS status until October 29, 2024. It's premature to list it as a system requirement.

  • Remove Node.js 22 from the requirements and keep only Node.js 20
  • Consider adding Node.js 22 support after it reaches LTS status in October 2024
🔗 Analysis chain

Verify Node.js 22 compatibility status

Since Node.js 22 is currently in development/beta status, we should verify if it's appropriate to recommend it in production requirements.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check Node.js 22 release status and @sylius-ui/admin compatibility

# Check latest @sylius-ui/admin package.json for Node.js engine requirements
curl -s https://registry.npmjs.org/@sylius-ui/admin/latest | jq '.engines.node'

# Check Node.js 22 release schedule and status
curl -s https://raw.githubusercontent.com/nodejs/Release/main/schedule.json | jq '.["v22"]'

Length of output: 312

@mpysiak mpysiak merged commit 222ff9f into Sylius:2.0 Dec 17, 2024
@github-actions
Copy link
Copy Markdown

github-actions bot commented Dec 17, 2024

Bunnyshell Preview Environment deployed

It will be automatically stopped in 4 hours.

Use the command /bns:start to start it if it's stopped.

Component Endpoints
mailhog https://mailhog-4gnk6b.bunnyenv.com/
php https://store-4gnk6b.bunnyenv.com/

Available commands:

  • /bns:stop to stop the environment
  • /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Documentation related issues and PRs - requests, fixes, proposals. Maintenance CI configurations, READMEs, releases, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants