Adding a "mixed" dev proxy #1219
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
softsimon
force-pushed
the
simon/add-mixed-proxy
branch
from
f97482e to
a45c371
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a middle ground between
npm run start:local-prodandnpm run startThe new
npm run start:mixedproxy will generally redirect all/api/endpoints to Mempool.space or Liquid.network depending on Base Module/api/v1/will redirect to the local NodeJS.This is very helpful during development when there is a lack of a proper Esplora backend setup.
It makes it easier to browse around and develop on pages like Liquid Assets.
mempool, liquid and bisq as Frontend Base Module is supported.