-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[Bug] .opencode/package-lock.json generated without respecting ~/.npmrc registry configuration #21079
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't workingcoreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)
Description
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.jsongeneration - Observe the generated
.opencode/package-lock.json
Screenshot and/or share link
No response
Operating System
macos
Terminal
iTerm2
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingcoreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)