-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: update root package.json configuration #28
Conversation
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including You can disable this status message by setting the WalkthroughThe changes in this pull request involve updates to the Changes
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
package.json (3)
20-22
: LGTM! Consider adding a comment for clarity.The new ngrok scripts are well-structured:
- The
_ngrok
script provides a reusable command for running ngrok.- The
ngrok
script uses dotenv to load environment variables before running_ngrok
.This setup allows for flexible and environment-specific ngrok configuration.
Consider adding a comment above these scripts to explain their purpose and usage, especially for new team members. For example:
// Ngrok scripts for exposing local server. Use `npm run ngrok` to start. "test": "vitest run", "_ngrok": "ngrok http 8000 --domain $NGROK_DOMAIN", "ngrok": "dotenv -e ./apps/api/.env -- npm run _ngrok"
29-30
: LGTM! Consider documenting usage in README.The addition of
cross-env
anddotenv-cli
as dev dependencies is appropriate:
cross-env
enables consistent environment variable usage across different platforms.dotenv-cli
facilitates loading environment variables from .env files, which is utilized in the newngrok
script.These additions enhance the project's capability for environment-specific configurations.
Consider adding documentation in the project's README or a separate CONTRIBUTING.md file explaining how these tools are used in the development workflow. This will help onboard new developers and ensure consistent usage across the team.
Line range hint
1-38
: Overall, these changes enhance the project's development setup.The modifications to
package.json
are well-structured and purposeful:
- The new ngrok scripts provide a consistent way to expose the local server.
- The addition of
cross-env
anddotenv-cli
improves environment variable management.These changes will likely streamline the development process, especially for tasks involving environment-specific configurations and local server exposure.
As the project grows, consider:
- Creating a separate documentation file (e.g.,
DEVELOPMENT.md
) detailing the usage of these new tools and scripts.- Setting up a pre-commit hook to ensure that sensitive information is not accidentally committed in .env files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job :) leaving one question.
package.json
Outdated
}, | ||
"dependencies": { | ||
"devcert": "^1.2.2", | ||
"rimraf": "^5.0.5" | ||
}, | ||
"devDependencies": { | ||
"cross-env": "^7.0.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this dependency? I don't see it being used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update!
Seems there a couple more things to adjust. Also leaving a question.
package.json
Outdated
}, | ||
"dependencies": { | ||
"@tabler/icons-react": "^3.19.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple things:
- I think you added tabler icons here by mistake?
- Didn't we need
dotenv-cli
? Isn't that package the one providing thedotenv
binary used by thengrok
command?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Updated the package.json to include necessary changes for project dependencies and configuration. Please review and let me know if any further adjustments are needed.
Summary by CodeRabbit
New Features
Improvements
dotenv-cli
.