You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Introduced a new section on Packagist Integration, explaining how Composer Update Helper fetches package information.
- Described the two-tier approach for fetching package data: direct Packagist API calls and fallback to `composer show`.
- Provided guidance on improving Packagist access through mirrors and private repositories.
- Included performance considerations and tips for optimal usage.
This update enhances the documentation to better inform users about dependency management and configuration options.
When the Packagist API doesn't have information about these packages, the tool automatically falls back to `composer show`, which respects your repository configuration.
250
+
251
+
#### Performance Considerations
252
+
253
+
- **API Rate Limiting**: Packagist doesn't enforce strict rate limits, but excessive requests may be throttled. The tool includes proper user-agent headers and reasonable timeouts (5 seconds).
254
+
255
+
- **Offline Mode**: If you're working offline or behind a firewall, the tool will fall back to `composer show`, which uses Composer's local cache when available.
256
+
257
+
- **Caching**: Composer caches package metadata automatically. Running `composer update` periodically ensures your cache is fresh, improving fallback performance.
258
+
259
+
> 💡 **Tip**: If you're using a VPN or behind a corporate firewall, configuring a Packagist mirror or ensuring `composer show` works will provide the best experience.
0 commit comments