chore: replace env-cmd with node builtin function

[joshunrau]

Summary by CodeRabbit

• New Features

  • Enhanced CLI commands now support a dedicated option for specifying an environment file (using flags like --env-file). Build, development, and start commands have been updated for direct environment file referencing, streamlining configuration.
  • Added a new method to load environment files, improving test capabilities.

• Chores

  • Removed an obsolete dependency to simplify the overall setup.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The modifications update the command scripts to directly reference environment files and remove the env-cmd dependency. The CLI now uses a centralized error handler (parseResult) and adds an option for specifying an environment file. Testing enhancements include new mocks for path resolution and verification that the environment file is correctly processed. Additionally, file resolution logic was refactored to separate file existence checks from extension validation, and a new helper function was added to support environment file loading in tests.

Changes

File(s)	Change Summary
package.json	Updated example script commands to directly reference the environment file and removed the env-cmd dependency.
src/cli/…/libnest.test.ts	Added a new mocked function (resolveAbsolutePath) and a test case to verify environment file handling with the --env-file option.
src/cli/libnest.js	Introduced the parseResult function for centralized error handling; added the -e, --env-file <path> option and updated the preSubcommand hook for environment file loading.
src/meta/resolve.ts	Renamed resolveAbsoluteImportPath to resolveAbsolutePath and introduced a new resolveAbsoluteImportPath to perform file extension validation.
src/testing/helpers/cli.ts	Added a loadEnvFile method as a mocked function in the process object for testing purposes.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant CLI as Libnest CLI
    participant Resolver as File Resolver
    participant Process as Process Loader

    U->>CLI: Execute command with --env-file
    CLI->>Resolver: resolveAbsolutePath(file, cwd)
    Resolver-->>CLI: Return result
    CLI->>CLI: parseResult(result)
    alt Valid result
        CLI->>Process: loadEnvFile(env file)
    else Error
        CLI-->>U: Throw InvalidArgumentError
    end
    CLI-->>U: Execute command and output

Loading

Possibly related PRs

• chore: replace env-cmd with node builtin function #35: The changes in the main PR are directly related to those in the retrieved PR, as both involve modifications to the same script commands in package.json to remove the env-cmd dependency and directly reference environment files.

Poem

I'm a rabbit with code so bright,
Hopping through changes in the night,
Scripts now shine with a direct clue,
Tests mock my path with a hop or two.
Error handling's smooth, my code's delight!
🎉🐇 Hop on, let's code on in pure flight!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 897cb7b and 35453f8.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

• package.json (1 hunks)
• src/cli/__tests__/libnest.test.ts (2 hunks)
• src/cli/libnest.js (2 hunks)
• src/meta/resolve.ts (1 hunks)
• src/testing/helpers/cli.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[github-actions]

🎉 This PR is included in version 4.3.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀