gemini-cli - 💡(How to fix) Fix refactor: move sandboxImageUri out of package.json 'config' to resolve npm warnings

npm warn Unknown cli config "sandboxImageUri" (@google/gemini-cli:sandboxImageUri). This will stop working in the next major version of npm.

TL;DR

Move the sandboxImageUri configuration from the config block to a custom top-level field in package.json to resolve the npm warning.

Guidance

• Identify the config block in package.json and locate the sandboxImageUri key.
• Create a new custom top-level field, such as sandboxConfig, in package.json.
• Move the sandboxImageUri key from the config block to the new sandboxConfig field.
• Verify that running npm run build no longer produces the unknown cli config warning.

Example

// Before
{
  "config": {
    "sandboxImageUri": "some-uri"
  }
}

// After
{
  "sandboxConfig": {
    "sandboxImageUri": "some-uri"
  }
}

Notes

This solution assumes that the sandboxImageUri configuration is not used by any other scripts or dependencies that rely on it being in the config block. Additional updates may be necessary to reference the new location of the configuration.

Recommendation

Apply workaround: Move the sandboxImageUri configuration to a custom top-level field, as this resolves the conflict with npm's internal configuration and prevents future warnings.