fix: resolve npm global module path on Windows

[elrrrrrrr]

Summary

On Windows, npm install -g --prefix installs packages to <prefix>/node_modules/<pkg>, while on Linux/macOS it installs to <prefix>/lib/node_modules/<pkg>.

The hardcoded lib/node_modules path in getUtooVersion() and npmLibDir caused setup-utoo to fail on Windows CI with:

Error: Utoo was installed but package.json could not be found or read

Fix

Add getNpmGlobalModulePath() helper that returns the correct path based on os.platform():

• Windows: <prefix>/node_modules/<pkg>
• Linux/macOS: <prefix>/lib/node_modules/<pkg>

Applied to both npmLibDir (cache paths) and getUtooVersion() (installation verification).

Test plan

• Windows CI in eggjs/egg should pass after this fix is released

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello, 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 resolves a critical cross-platform compatibility issue within the setup-utoo action, specifically concerning how global npm modules are located. By introducing an OS-aware path resolution mechanism, the action can now correctly identify the utoo package's installation directory on both Windows and Unix-like systems, preventing failures during setup and verification.

Highlights

• Cross-platform npm global module path resolution: Addressed the difference in how npm global packages are installed on Windows versus Linux/macOS, where Windows uses <prefix>/node_modules/<pkg> and Unix-like systems use <prefix>/lib/node_modules/<pkg>.
• New helper function getNpmGlobalModulePath(): Introduced a new utility function, getNpmGlobalModulePath(), to dynamically determine the correct global module path based on the operating system.
• Integration of path resolution: Applied the new getNpmGlobalModulePath() helper to both the npmLibDir variable (for cache paths) and within the getUtooVersion() function (for installation verification) to ensure consistent and correct path resolution across platforms.

Changelog

• src/action.ts
  • Imported the platform function from node:os to enable OS detection.
  • Modified the npmLibDir calculation to utilize the new getNpmGlobalModulePath helper for accurate path resolution.
  • Updated the getUtooVersion function to use getNpmGlobalModulePath for locating the utoo package's package.json.
  • Added a new helper function getNpmGlobalModulePath to encapsulate the logic for determining OS-specific global module paths.

Activity

• No human activity has been recorded 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. ↩

[gemini-code-assist]

Code Review

This pull request correctly addresses an issue with resolving npm global module paths on Windows by introducing a helper function, getNpmGlobalModulePath, that generates the correct path based on the operating system. The change is well-implemented and fixes the described bug. I have one minor suggestion to improve code maintainability by reducing a small amount of code duplication.

[gemini-code-assist]

While extracting the prefix calculation into a variable improves readability here, the same logic (binPath.replace(/[\/\\]bin$/, "")) is also present in the installUtoo function on line 167. To avoid this duplication and improve maintainability, consider extracting this logic into a dedicated helper function.

For example:

function getNpmPrefixFromBinPath(binPath: string): string {
  return binPath.replace(/[\/\\]bin$/, "");
}

This new function could then be used both here and in installUtoo.