fix: fix error when execute pnpm dev command

[kagol]

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features
  • Integrated the Quill rich text editor for enhanced text editing capabilities.

[coderabbitai]

Walkthrough

The pull request introduces a new dependency, quill, version ^2.0.0, to the package.json file. This addition integrates the Quill rich text editor into the project, enhancing text editing capabilities. The existing dependencies in the file remain unchanged, maintaining the overall structure of package.json.

Changes

File	Change Summary
package.json	Added "quill": "^2.0.0" to dependencies

Assessment against linked issues

Objective	Addressed	Explanation
N/A	❌	No linked issues provided for assessment.

Possibly related issues

• No related issues identified as none were provided.

🐰 In the meadow, a new tool we find,
Quill brings text editing, oh so refined!
With rich features to edit and play,
Our project shines brighter, hip-hip-hooray!
Let's hop along, with joy in our heart,
For every new change is a wonderful start! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 72062af and b9fff00.

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 not posted (1)

package.json (1)

42-43: Dependency addition looks good, but consider using a more specific version range.

The addition of the quill dependency aligns with the PR objective. However, consider using a more specific version range like ~2.0.0 instead of ^2.0.0 to avoid potential breaking changes from minor version updates.

Also, verify that quill is being used correctly in the codebase by running the following script:

Verification successful

---

The quill dependency is actively used and correctly integrated in the codebase.

The verification confirms that the quill dependency is imported and utilized across multiple files, with several instances of module registration using Quill.register. This indicates proper integration and usage of the library. No direct instantiation with new Quill was found, which aligns with common usage patterns where Quill is extended or configured rather than instantiated directly.

• Files with Quill imports and registrations are primarily located in the packages/fluent-editor/src directory.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the `quill` dependency.

# Test 1: Search for import statements. Expect: At least one import statement.
rg --type typescript --type javascript $'import .* from [\'"](quill|@opentiny/fluent-editor)[\'"]' 

# Test 2: Search for Quill class usage. Expect: At least one usage.
rg --type typescript --type javascript $'new Quill' -A 2

# Test 3: Search for Quill module registration. Expect: At least one module registration.
rg --type typescript --type javascript $'Quill\.register' -A 2

Length of output: 330

---

Script:

#!/bin/bash
# Description: Verify the usage of the `quill` dependency.

# Test 1: Search for import statements. Expect: At least one import statement.
rg 'import .* from [\'"](quill|@opentiny/fluent-editor)[\'"]' 

# Test 2: Search for Quill class usage. Expect: At least one usage.
rg 'new Quill' -A 2

# Test 3: Search for Quill module registration. Expect: At least one module registration.
rg 'Quill\.register' -A 2

Length of output: 94

---

Script:

#!/bin/bash
# Description: Verify the usage of the `quill` dependency.

# Test 1: Search for import statements. Expect: At least one import statement.
rg "import .* from ['\"](quill|@opentiny/fluent-editor)['\"]" 

# Test 2: Search for Quill class usage. Expect: At least one usage.
rg "new Quill" -A 2

# Test 3: Search for Quill module registration. Expect: At least one module registration.
rg "Quill\.register" -A 2

Length of output: 9259

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 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.