Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(apis): if api.npms.io is down, fallback to registry.npmjs.org #7

Merged
merged 2 commits into from Apr 24, 2018

Conversation

Projects
None yet
1 participant
@topheman
Copy link
Owner

topheman commented Apr 24, 2018

In case api.npms.io is unavailable, the app seamlessly falls back to the npm registry api.
The user wont even notice it. There will be zero downtime.

Why keep api.npms.io ? It has better indexing/search results.
Internally input/output of both apis are shaped the same way (so they can be switched).

topheman added some commits Apr 24, 2018

feat(apis): if api.npms.io is down, fallback to registry.npmjs.org
In case api.npms.io is unavailable, the app seamlessly falls back to the npm registry api.
The user wont even notice it. There will be zero downtime.

Why keep api.npms.io ? It has better indexing/search results.
Internally input/output of both apis are shaped the same way (so they can be switched).

@topheman topheman merged commit 3336acd into master Apr 24, 2018

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@topheman topheman deleted the feat/api-fallback branch Apr 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.