urql
ramda
urql | ramda | |
---|---|---|
17 | 80 | |
8,489 | 23,584 | |
0.4% | 0.2% | |
9.0 | 6.8 | |
3 days ago | 6 days ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
urql
-
Top React Data Fetching Libraries
urql (8k β) -> A highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
-
Apollo Layoffs
Eh, https://github.com/urql-graphql/urql is considered the improved re-architected project that doesn't contain the legacy baggage from the beginning of GraphQL like Apollo does.
-
React Real Time Messaging With GraphQL
urql docs
-
SvelteKit Server-Side Rendering (SSR) with @urql/svelte
Even though I think this solution is not too bad, I wish @urql/svelte would implement a better way to handle SSR with sveltekit. I posted a question on the urql GitHub discussions board, but I have not gotten any response yet.
- Conditionally rendering
-
End-to-end GraphQL error handling?
I want to share my approach to handling errors in GraphQL resolvers (I use GraphQL Yoga on the server-side) and pass them to the frontend side (where I use Svelte + @urql/svelte).
-
Svelte GraphQL Resources
Repository
-
Open sourcing a privacy-friendly and customizable Disqus alternate ππ₯
API client: urql
-
gQuery 101 β A Svelte Kit Focused GraphQL Library
big thread on it here https://github.com/FormidableLabs/urql/issues/1819
-
If every component made it's own API call to get the data, would that be an overkill for the server?
Here is link number 1 - Previous text "way"
ramda
-
Tacit Programming
JavaScript is great for point-free programming! Make sure you check out Ramda.js https://ramdajs.com/
Itβs fun in the sense that solving a puzzle is fun, but I avoid it for anything I need to maintain long-term.
But itβs good practice for understanding combinators which is useful for some kinds of problems.
-
Pipeline-Oriented Programming [video]
This is very cool. I remember I got sucked into things like Ramda going down this functional programming rabbit hole :-)
https://ramdajs.com/
-
Level up your Typescript game, functionally - Part 2
To create our pipeline, I'm going to use the pipe function from the NodeJS ramda library instead of building my own.
-
Level up your Typescript game, functionally - Part 3
Other libraries to check out are pratica and ramda
- Ramda: A practical functional library for JavaScript programmers
-
FP and JavaScript/TypeScript
I recently took ownership of the new types/ramda repo. This repo is re-exported by @types/ramda and is the first step to bringing type definitions for ramda in-house. We're already hard at work correcting major issues, adding full currying support, and general bug fixes
- [AskJS] Auto-Generated Documentation from JSDoc comments, nice modern themes?
-
When to use currying in JavaScript
I'm going to be honest. You probably don't need to use currying in JavaScript. In fact, trying to fit it in your code is going to do more harm than good, unless it's just for fun. Currying only becomes useful when you fully embrace functional programming, which, in JavaScript, means using a library like Ramda instead of the standard built-in functions.
-
No Lodash
Lodash gets so many things wrong Iβd rather not see it in most projects. I appreciate a good utility library for JS projects but my go-to choice has to be Ramda[1]. Every function it exports is curried and works great with pipe which enables me to write highly reusable and composable functions in pointfree notation. I have never been as productive with lodash, and I find the functional style easier to read
[1] https://ramdajs.com/
-
Snap.js - A competitor to Lodash
Do note though that ramda is different from rambda. π (Granted they are very similar!)
What are some alternatives?
react-query - π€ Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
lodash - A modern JavaScript utility library delivering modularity, performance, & extras.
apollo-client - :rocket: Β A fully-featured, production ready caching GraphQL client for every UI framework and GraphQL server.
Rambda - Faster and smaller alternative to Ramda
apollo - π Apollo/GraphQL integration for VueJS
RxJS
SWR - React Hooks for Data Fetching
immutable-js - Immutable persistent data collections for Javascript which increase efficiency and simplicity.
graphql-request - Minimal GraphQL client
fp-ts - Functional programming in TypeScript
react-relay - Relay is a JavaScript framework for building data-driven React applications.
lazy.js - Like Underscore, but lazier