Bump cross-spawn from 7.0.3 to 7.0.6

[dependabot]

Bumps cross-spawn from 7.0.3 to 7.0.6.

Changelog

Sourced from cross-spawn's changelog.

7.0.6 (2024-11-18)

Bug Fixes

• update cross-spawn version to 7.0.5 in package-lock.json (f700743)

7.0.5 (2024-11-07)

Bug Fixes

• fix escaping bug introduced by backtracking (640d391)

7.0.4 (2024-11-07)

Bug Fixes

• disable regexp backtracking (#160) (5ff3a07)

Commits

• 77cd97f chore(release): 7.0.6
• 6717de4 chore: upgrade standard-version
• f700743 fix: update cross-spawn version to 7.0.5 in package-lock.json
• 9a7e3b2 chore: fix build status badge
• 0852683 chore(release): 7.0.5
• 640d391 fix: fix escaping bug introduced by backtracking
• bff0c87 chore: remove codecov
• a7c6abc chore: replace travis with github workflows
• 9b9246e chore(release): 7.0.4
• 5ff3a07 fix: disable regexp backtracking (#160)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[codara-ai-code-review]

Potential issues, bugs, and flaws that can introduce unwanted behavior

1. Version Inconsistency:

   • /package-lock.json - The upgrade from "fumadocs-core": "^13.4.10" to "fumadocs-core": "^14.7.7" could introduce breaking changes if the new version has significant differences in functionality or behavior that the rest of the codebase is not prepared to handle.

2. Peer Dependency Management:

   • /package-lock.json - The introduction and modification of peer dependencies, particularly for "@orama/tokenizers", "@oramacloud/client", "algoliasearch", "next", "react", and "react-dom" should be reviewed carefully. If these peer dependencies are not aligned with the expected versions in other packages, it could lead to compatibility issues during runtime.

3. New Packages Dependencies:

   • /package-lock.json - The addition of "emoji-regex-xs": "^1.0.0" and other new packages might introduce new vulnerabilities. It’s crucial to review these additions for any potential security issues.

4. Sub-package Versioning:

   • /package-lock.json - The sub-package versions under node_modules/fumadocs-ui/node_modules refer to older versions (like fumadocs-core at 13.4.10) which might not be compatible with the newly installed top-level fumadocs-core package if API changes exist.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency

1. Locking Version Ranges:

   • /package-lock.json - Consider using fixed versions instead of caret ranges for critical dependencies to ensure the environment remains consistent and to avoid introducing unintended breaking changes from minor updates.

2. Audit Dependencies Regularly:

   • /package-lock.json - Implement a periodic review process for the dependencies to check for updates or known vulnerabilities. Tools like npm audit can be used to automate this process.

3. Peer Dependency Clarity:

   • /package-lock.json - Clearly define peer dependencies by locking to a specific version range rather than a wildcard "*" to prevent unintended upgrades when consumers of the package might not be compatible with the latest versions.

4. Remove Unused Dependencies:

   • /package-lock.json - Review the list of dependencies and ensure that all are necessary for the project. Unused or duplicate dependencies should be removed to maintain a cleaner project structure and potentially reduce the risk of security vulnerabilities.

5. Documentation and Comments:

   • /package-lock.json - Adding comments about why specific packages are updated or introduced can be helpful for context in future maintenance. This kind of documentation fosters better project governance and facilitates onboarding new team members.