651 run migration files as js file

[ae2079]

Resolve this issue: #651

Summary by CodeRabbit

• Chores
  • Updated migration scripts for different environments to ensure compatibility with production builds.

[coderabbitai]

Walkthrough

The recent changes streamline the migration scripts for different environments by adjusting the paths and commands for running and reverting migrations. Specifically, the scripts now use compiled JavaScript files in production and TypeScript files in other environments. Additionally, the configuration file ormconfig.ts has been updated to conditionally set the migrations property based on the environment.

Changes

Files	Change Summary
package.json	Updated migration scripts to use typeorm commands with adjusted paths for production environment.
src/ormconfig.ts	Introduced conditional logic to set the migrations property based on the environment (production or not).

Sequence Diagram(s) (Beta)

sequenceDiagram
    participant Developer
    participant Package.json
    participant Ormconfig.ts
    participant TypeORM

    Developer->>Package.json: Run migration script
    Package.json->>TypeORM: Execute migration command with environment-specific path
    TypeORM->>Ormconfig.ts: Load configuration
    Ormconfig.ts->>TypeORM: Provide environment-specific migration settings
    TypeORM->>Database: Run or revert migrations

Loading

Poem

In the code where changes bloom,
Paths now clear, no more gloom.
TypeScript here, JavaScript there,
Migrations run with utmost care.
Configs shift with the breeze,
Environment set with ease.
🎉 Hooray, the code's in tune! 🌟

---

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 f09a0ad and cf98f98.

Files selected for processing (2)

• package.json (1 hunks)
• src/ormconfig.ts (2 hunks)

Additional context used

Biome

src/ormconfig.ts

[error] 42-44: A global variable should not be reassigned. (lint/suspicious/noGlobalAssign)

Assigning to a global variable can override essential functionality.

Additional comments not posted (3)

src/ormconfig.ts (1)

23-23: The import of ENVIRONMENTS is correctly placed and necessary for the conditional logic below.

package.json (2)

212-212: The updated migration run script correctly points to the JavaScript configuration file and uses the typeorm CLI directly, aligning with the PR objectives.

---

213-213: The updated migration revert script is consistent with the migration run script and correctly uses the JavaScript configuration file.