chore: Add .direnv file for automatic Node.js version switching with fnm

[Amosel]

What is the purpose of the change

Added .direnv config, to support that allows fnm to automatically switch Node.js version.

ClickUp Task

ClickUp Task URL

Brief Changelog

Testing and Verifying

Documentation and Release Note

Summary by CodeRabbit

• Chores
  • Enhanced Node.js version management to automatically align with the version specified in package.json.

[coderabbitai]

Walkthrough

The update introduces the use_node() function in the .envrc file, which dynamically sets the Node.js version for the project environment based on the version specified in the package.json file, using fnm.

Changes

Files	Change Summary
.envrc, .nvmrc	Added use_node() function to set Node.js version to v20.11.1 using fnm based on package.json

🐰✨
In the realm of code, under the digital sky,
A rabbit hopped, with a twinkle in its eye.
"Let's sync our Node, with a magical spell,"
It said, as fnm rang like a bell.
Now versions align, with a whisper of JSON,
In this digital burrow, where innovation is born.
🌟🐾

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/coderabbit-overrides.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.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
osmosis-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2024 11:20pm
osmosis-frontend-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2024 11:20pm
osmosis-frontend-edgenet	❌ Failed (Inspect)			Apr 2, 2024 11:20pm
osmosis-testnet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2024 11:20pm

[jonator]

What about nvm? Also, do these tools offer this functionality of automatically switching version based on package.json engine?

[jonator]

It's worth mentioning- for my purposes I use nvm and set the latest as a default alias. Perhaps devs can do something similar then we don't have to concern ourselves with maintaining this for all devs.

[Amosel]

You're right, this is narrowing the solution. Plus, version resolution is not trivial.
With .nvmrc we don't get unpredictable results looking forwards.

(forced a new commit)

[Amosel]

I use fnm:

You can use fnm use --resolve-engines to get the version that is pegged.
You can also add eval "$(fnm env --use-on-cd)" your shell to automatically update