Update client-libraries.md #67
Closed
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
We recently release an early version of https://github.com/wp-headless/fetch that is now being used in production. It's not an easy decision to fragment the ecosystem when there are other offerings. We believe our approach is significantly different enough to warrant this risk. We did so for the following reasons: * Long unresolved [browser issues](WP-API/node-wpapi#438) * Bloated [packages size](https://bundlephobia.com/result?p=wpapi@0.12.1) * No [tree-shakable](https://webpack.js.org/guides/tree-shaking/) ESM or CJS build available * Opinionated API that attempts to do more then is needed. * Lack of automated browser testing and coverage * + more wp-headless/fetch will be a valuable option to the community and therefore should be listed. Thanks! :-)
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.
We recently release an early version of https://github.com/wp-headless/fetch that is now being used in production.
It's not an easy decision to fragment the ecosystem when there are other offerings. We believe our approach is significantly different enough to warrant this risk. We did so for the following reasons:
wp-headless/fetch will be a valuable option to the community and therefore should be listed. Thanks! :-)