feat: support devEngines.runtime in deno

[risu729]

This PR adds support for parsing devEngines.runtime configuration for deno in package.json file.
This allows mise to detect Deno versions specified in the devEngines section, similar to Node.js.
https://pnpm.io/package_json#devenginesruntime

Changes

• src/plugins/core/deno.rs: Updated parse_idiomatic_file to check for package.json and parse devEngines.runtime for deno.
• src/package_json.rs: Added a test case for deno in devEngines.

Verification

• Added a new test case test_deno_dev_engines in src/package_json.rs.
• Ran cargo test package_json to verify the functionality.

[gemini-code-assist]

Summary of Changes

Hello @risu729, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances mise's Deno plugin by enabling it to read Deno version requirements from the devEngines.runtime section of package.json. This change allows for more flexible and standardized version management for Deno projects, aligning its behavior with how other runtimes might be configured, and ensures that mise can correctly identify and use the specified Deno environment.

Highlights

• Deno Version Detection: Added support for mise to detect Deno versions specified within the devEngines.runtime field of package.json files.
• Package.json Parsing: The Deno plugin now includes package.json in its list of idiomatic filenames and implements logic to parse it for Deno runtime versions.
• Test Coverage: A new test case was introduced in src/package_json.rs to verify the correct parsing of Deno versions from devEngines.runtime.

Changelog

• src/package_json.rs
  • Added test_deno_dev_engines to validate parsing of Deno versions from devEngines.runtime in package.json.
• src/plugins/core/deno.rs
  • Modified idiomatic_filenames to include package.json as a recognized file for Deno version detection.
  • Implemented parse_idiomatic_file to extract the Deno version from package.json's devEngines.runtime field.

Activity

• No human activity has occurred on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[Copilot]

Pull request overview

This PR adds support for detecting Deno versions from the devEngines.runtime field in package.json files, bringing Deno inline with Node.js and Bun which already support this feature. This allows mise to automatically detect and install the appropriate Deno version when a project specifies it in their package.json.

Changes:

• Added package.json support to Deno's idiomatic file detection
• Implemented parsing of devEngines.runtime.deno from package.json
• Added unit test coverage for Deno in devEngines

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/plugins/core/deno.rs	Added package.json to idiomatic filenames and implemented parse_idiomatic_file to extract Deno version from devEngines.runtime
src/package_json.rs	Added test case to verify Deno version extraction from devEngines.runtime field

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gemini-code-assist]

Code Review

This pull request adds support for devEngines.runtime for Deno in package.json, allowing mise to detect Deno versions from it. The changes are well-implemented, including an update to the Deno plugin to parse package.json and a new test case to verify the functionality. The code is correct and follows the existing patterns in the codebase. I have no issues with the proposed changes.