searchkit
rfcs
searchkit | rfcs | |
---|---|---|
5 | 98 | |
4,714 | 5,399 | |
0.3% | 0.7% | |
7.6 | 2.9 | |
2 days ago | 5 months ago | |
TypeScript | ||
Apache License 2.0 | 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.
searchkit
-
Autocomplete β a JavaScript library for building autocomplete experiences
https://github.com/searchkit/searchkit is an instantsearch adapter for elasticsearch / opensearch
-
React.dev
One example of this pattern is Searchkit [0] which performs most of its logic inside a singleton Searchkit class which is instantiated and passed as a prop to the root React component. A bonus is that it's easier to implement bindings for Angular, Svelte, etc. since they can rely mostly on the class. For example, it looks like Searchkit now suggests using InstantSearch (react-instantsearch-dom) [1] from Algolia, i.e. an entirely different maintainer, and it creates the bindings with a `Client(new SearchKit(...))` adapter [2] around the class (see the code on the home page at [0]).
[0] https://www.searchkit.co/
[1] https://github.com/algolia/instantsearch
[2] https://github.com/searchkit/searchkit/blob/main/packages/se...
- I made Elasticsearch work with Algolia's Instantsearch
-
How to build an availability search UI with Elasticsearch
We will use React, Next.JS, Instantsearch and Searchkit to build a search UI.
-
Ask HN: Should I give up and get a job?
I think you are probably spending too much of your time on software and too little time on marketing.
When I look at an open-source project, I ask myself three things:
1) What does it do exactly?
2) Is this easy to get started with?
3) Does it have any documentation?
For example, I have a use case for wanting to use graphql to communicate with elasticsearch. I google "graphql + elasticsearch" and somewhere a link to https://www.searchkit.co/ comes up. I look at it and I find my answers within 60 seconds:
1) Top of the page I see "Searchkit is an open source library which helps you build a great search experience with Elasticsearch. Powered by Apollo GraphQL." This makes me think that yeah, it's probably looking to solve a similar problem to me. In case I had any doubts, there's a demo.
2) Yes, easy to get started. There's a big "get started" button at the top of the page. And a get-started-video link at the bottom of the homepage.
3) At a glance, yes, it has decent documentation.
Given that I quickly got answers to these 3 questions, yes, I might consider using this project, or at least trying it out.
When I go to your page, I see:
1) River DB is a Rust connection pool and middleware proxy... ok... why do i need that? What problem is this solving? There's a long paragraph I can read after that, but when i'm browsing the web i don't usually read long paragraphs, so you've lost me already.
2) I have no idea how to get started
3) Doesn't look like there's any docs
Given the above, why would I use your software?
Note that the above has nothing to do with your software quality. But people only care about your code if things are breaking. Marketing material is what gets them in the door. For example, I use React all the time. I have NO IDEA if the underlying code is any good. And I don't really care. What I care about is that it's easy to use.
Anyway, long story short... if you want to build a software business, coding is maybe 30-40% of the job. Marketing, sales, documentation and all that jazz is probably the majority of the work. If you don't want to do that and you just want to code, then great, get a job. People will pay you good money for that.
rfcs
-
React Labs: What We've Been Working On β February 2024 β React Compiler
Examples from the conversations of that time:
> ...we want closures to capture the values we rendered with, and to keep "seeing" those values forever. That's really important for concurrent mode where a notion of current value doesn't really exist. Hooks design models a component as being in many non-clashing states at the same time, instead of switching the "current" state (which is what classes model well). People don't really need to think about these details, but they're motivating the design a lot. [0]
> In Concurrent Mode, render may run more then one time, and since this in a class is mutable, renders that should be the same may not be. [1]
[0] - https://github.com/reactjs/rfcs/pull/68#issuecomment-4778866...
[1] - https://tkplaceholder.io/why-function-components-fit-react-b...
- A modest request: How do you fetch data in React 18+ WITHOUT a third party dependency?
-
Optimizing performance: how our extension became lightning fast
There are multiple names for this hook. You can find the documentation under the names useEvent or useEffectEvent.
-
The Sisyphean Quest for Web Performance
-https://www.patterns.dev/ -https://github.com/reactjs/rfcs/blob/main/text/0188-server-components.md -https://dev.to/this-is-learning/qwik-the-post-modern-framework-3c5o -https://dev.to/this-is-learning/astro-framework-169m -https://developers.google.com/web/updates/2019/02/rendering-on-the-web -https://web.dev/vitals/
- Why Do I Need RSC(react server components) if I Already Have Remix
-
Declaring JSX types in TypeScript 5.1
However, in React, function components can return a ReactNode. This type includes number | string | Iterable | undefined and will likely also include Promise( in the future.
-
Is ESLint Exhaustive Deps a bad rule (sometimes)?
I was also hoping that useEvent would eliminate some weird dependency cases, who knows when that will actually happen (https://github.com/reactjs/rfcs/pull/220).
-
Returning to React and looking for modern expert to sanity check
Given a lot of unknowns on SSR and ReactEng working on RSC it feels like the wrong move to use next.js and I should just use normal react. For basic react is create react app the way to go or vite?
-
Server Components vs. SSR in Next.js
As mentioned before, Next.js takes a stance of treating every component as a Server Component by default. If you want to use a Client Component, you'll need to annotate the file with use client; directive at the top of the component file.
-
Is it a bad idea to use the experimental "/app" directory in a professional project?
Use client is actually a React convention for what itβs worth. https://github.com/reactjs/rfcs/pull/227
What are some alternatives?
semantic-ui-react - The official Semantic-UI-React integration
server - Tolgee is translation management cloud platform made for translating modern web applications. It works great with JS frameworks like React, Angular, Vue and others. [Moved to: https://github.com/tolgee/tolgee-platform]
sveltekit-graphql-github - Use Apollo Client with SvelteKit to Query a GraphQL API: we use the GitHub API to query our repos and learn a bit of SvelteKit along the way.
use-context-selector - React useContextSelector hook in userland
rctui - A collection of components for React, base on bootstrap 4.0.
react-refresh-webpack-plugin - A Webpack plugin to enable "Fast Refresh" (also previously known as Hot Reloading) for React components.
pivotal-ui-react - Pivotal's design system & component library
react-18 - Workgroup for React 18 release.
cdbreact - Contrast Design Bootstrap : Elegant UI Kit and reusable components for building mobile-first, responsive websites and web apps
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
react-uikit-components - React UIkit Components for the UIKit CSS framework
react-redux - Official React bindings for Redux