modify --openssl-legacy-provider in pacakge

[iMnoorfahad]

Description

This pull request addresses the issue related to the OpenSSL error stack, specifically:

{
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

The problem has been resolved by adding the --openssl-legacy-provider flag in the start script as follows:

"start": "yarn buildThemes && craco --openssl-legacy-provider start"

This change fixes the issue # (replace with the relevant issue number).

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

I have tested this change locally by running the updated start script with the --openssl-legacy-provider flag. The application started without encountering the OpenSSL error mentioned above.

To test this change:

1. Clone this repository.
2. Install dependencies with yarn install.
3. Run the start script with the yarn start.

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.

Summary by CodeRabbit

• Chore
  • Modified project build and start scripts to include compatibility flags.

[coderabbitai]

Walkthrough

This update introduces a modification to the start and build scripts in the package.json by appending the --openssl-legacy-provider flag to the craco command. This adjustment aims to address issues related to OpenSSL errors during the project's initialization and build processes.

Changes

File	Change Summary
package.json	Added --openssl-legacy-provider to start and build scripts

Possibly related issues

• Encountering ERR_OSSL_EVP_UNSUPPORTED Error During Project Initialization #287: The issue reports ERR_OSSL_EVP_UNSUPPORTED errors which are directly addressed by the inclusion of the --openssl-legacy-provider flag in this PR. This change should help in resolving the OpenSSL related initialization error described.

🐰✨
A little flag in scripts so neat,
Helps OpenSSL not admit defeat.
With craco now gently tweaked,
No more errors shall be leaked.
Hop, hop, hurray, let's start the feat! 🚀
🐰✨

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e4b9416 and 7396e19.

Files selected for processing (1)

• package.json (1 hunks)

Additional comments not posted (1)

package.json (1)

71-72: The inclusion of --openssl-legacy-provider in both start and build scripts is a suitable workaround for the OpenSSL error. Ensure that all environments where the project will be built or run support this flag.

---

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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[ar-dehghan-a]

I did this method and it works