fix(bug): error caused by slugify made server unable to start

[toema]

Downgrade @sindresorhus/slugify to resolve ESM compatibility issue

Changes

• Downgraded @sindresorhus/slugify from 2.2.1 to 1.1.2

Why

Version 2.x is purely ESM which causes compatibility issues with the current CommonJS setup in the server application. Version 1.1.2 maintains CommonJS support while providing the same functionality.

Testing

• Server starts successfully
• Slug generation works as expected
• No ESM-related errors in the console

Related Issues

Fixes server startup error caused by ESM/CommonJS module incompatibility

Summary by CodeRabbit

• Chores
  • Adjusted an internal dependency version to maintain overall system stability and compatibility.

[coderabbitai]

📝 Walkthrough

Walkthrough

The update downgrades the version of the @sindresorhus/slugify package in the package.json file from "^2.2.1" to "1.1.2". This change affects only the version specification of this dependency without modifying any other aspects of the file.

Changes

File	Change Summary
package.json	Downgraded @sindresorhus/slugify dependency from "^2.2.1" to "1.1.2"

Poem

Hop along in lines of code,
A downgrade story now unfolds.
With a twitch of my floppy ear,
I celebrate this change so clear.
Code-hopping through both new and old,
My rabbit heart sings bright and bold!

---

📜 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 cd21860 and ca54fd3.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

175-175: Downgraded dependency meets compatibility requirements.
The change correctly updates @sindresorhus/slugify to "1.1.2" to ensure continued support for CommonJS, thus resolving the server startup issue related to ESM incompatibility. Please ensure that the lock file (e.g., package-lock.json or yarn.lock) is updated accordingly to reflect this change and avoid any potential dependency conflicts.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.