Change NODE_ENV value to 'development' temporarily for enabling Devtools

[devleejb]

What this PR does / why we need it:
This PR temporarily changes the value of NODE_ENV from 'production' to 'development' to enable the Devtools for debugging purposes.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:
In order to activate Devtools and facilitate debugging, it is necessary to set the environment to 'development' temporarily. This adjustment allows for better visibility and control during the debugging process.

Does this PR introduce a user-facing change?:

NONE

Additional documentation:

Checklist:

• Added relevant tests or not required
• Didn't break anything

Summary by CodeRabbit

• Chores
  • Updated environment configuration for production setup.

[coderabbitai]

Walkthrough

The latest update to the project involves modifying the frontend/.env.production file by adding a specific environment variable, NODE_ENV, and setting it to "development." This change aims to configure the environment settings for proper execution during the development phase.

Changes

File Path	Change Summary
frontend/.env.production	Added NODE_ENV with the value "development"

Sequence Diagram(s)

No sequence diagrams are needed for this specific change.

Poem

A tweak to the code, for better days,
Environment set, in careful ways.
NODE_ENV now reads "development" bright,
Guiding our ship, through code's dark night.
With clarity now, our app takes flight. 🚀

---

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

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.

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 89dc5d5 and 15d0dec.

Files selected for processing (1)

• frontend/.env.production (1 hunks)

Additional context used

Gitleaks

frontend/.env.production

4-4: Detected a Generic API Key, potentially exposing access to various services and sensitive operations. (generic-api-key)

Additional comments not posted (1)

frontend/.env.production (1)

1-1: Ensure temporary changes are safe for deployment.

Setting NODE_ENV to 'development' is necessary for enabling Devtools as mentioned. However, ensure there are safeguards or reminders to switch it back to 'production' to avoid potential security risks or performance issues in a live environment.

[coderabbitai]

Remove exposed API key.

The API key found in the environment file could lead to unauthorized access if exposed in a public repository. Consider using environment variables managed by a secure service or encrypting sensitive information.

- VITE_YORKIE_API_KEY="cbovg64qfu96agb5i0fg"
+ VITE_YORKIE_API_KEY=${{ secrets.YORKIE_API_KEY }}

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	VITE_YORKIE_API_KEY="cbovg64qfu96agb5i0fg"
	VITE_YORKIE_API_KEY=${{ secrets.YORKIE_API_KEY }}

Tools

Gitleaks

4-4: Detected a Generic API Key, potentially exposing access to various services and sensitive operations. (generic-api-key)