Description
When opencode generates the .opencode/package-lock.json file , it does not respect the registry configuration specified in the user's ~/.npmrc file. The generated package-lock.json appears to use default npm registry settings instead of user-configured values.
Expected Behavior
When generating .opencode/package-lock.json, opencode should read and respect the npm repository configuration from ~/.npmrc, including:
- Custom registry URLs
- Any other relevant npm configuration
Actual Behavior
The generated .opencode/package-lock.json does not reflect the user's ~/.npmrc configuration. It seems to ignore the registry field entirely when resolving package dependencies.
Plugins
omo
OpenCode version
1.3.15
Steps to reproduce
- Use the latest version of opencode
- Run opencode command that triggers
package-lock.json generation
- Observe the generated
.opencode/package-lock.json
Screenshot and/or share link
No response
Operating System
macos
Terminal
iTerm2
Description
When opencode generates the
.opencode/package-lock.jsonfile , it does not respect theregistryconfiguration specified in the user's~/.npmrcfile. The generatedpackage-lock.jsonappears to use default npm registry settings instead of user-configured values.Expected Behavior
When generating
.opencode/package-lock.json, opencode should read and respect the npm repository configuration from~/.npmrc, including:Actual Behavior
The generated
.opencode/package-lock.jsondoes not reflect the user's~/.npmrcconfiguration. It seems to ignore theregistryfield entirely when resolving package dependencies.Plugins
omo
OpenCode version
1.3.15
Steps to reproduce
package-lock.jsongeneration.opencode/package-lock.jsonScreenshot and/or share link
No response
Operating System
macos
Terminal
iTerm2