I built dailypush.dev - a search engine for dev blog posts, summarized and curated by other devs

GaelS — Tue, 13 May 2025 12:09:00 +0000

Between newsletters, framework blogs, niche sources that post once a month, and the ones we just forget to check...

It's getting hard to follow the dev ecosystem and even harder to find what’s worth reading.

So I built dailypush.dev, a search engine for real dev blog posts.

🧠 What it does:

1300+ articles already indexed and counting every day
Pulled from hundreds of developer blogs and sources
Each post is summarized using GPT
Tagged by topic (React, backend, AI, DevOps…)
You can search, filter, and like posts you find valuable
Popular content surfaces naturally based on views and upvotes

✨ Why I made it

I kept missing solid blog posts buried in newsletters, tweets, changelogs, and Medium SEO traps.

I wanted a single place to stay up to date and search blog posts like a developer with summaries, clean metadata, and no fluff.

Ultimately, the goal is to make this curated by developers, for developers.

🚧 It’s a v1 and it's (hopefully) just the beginning

If there's traction, here’s what’s planned:

Personalized digests
Tag subscriptions
Saved posts & bookmarks
Recommendations by interest

📬 Would love your feedback, ideas, or use cases.

Try it here → https://dailypush.dev

(no signup required)

Thanks for reading 🙌

An alternative to handle state in React: the URL !

GaelS — Fri, 01 Jun 2018 08:31:52 +0000

For a french version of this article, go here :)

The state of a react app

Managing the global state of a React app is an endless war between libraries. Therefore, in order to add my 2 cents, we'll see how to do the exact same thing using the URL and react-router.

URL FTW

In single page application, the URL does not really matter. Most of the time, it is just an endpoint to request all the assets and that's it.

Landing on https://myApp.io ou https://myApp.io?user=gael&job=dev would have no impact on what you'll see on the first loading of the app.

Let's change that.

Some code

I started to use develop this idea in a side project (code and demo to play with :))

However, for this article, I have redeveloped a codesandbox to focus only on what matters for here.

First of all, how will we use the URL ?

Well, we'll use everything located after the ? in the URL, the so-called search params.

Some docs here on the subject.

Get values from the URL

In the context of this article, we are going to look for only one parameter that we'll name query.

To retrieve that parameter (if it is indeed in the URL eg. https://myApp.io?query=javascript ), we are going to check the ... search params. Luckily, they are easy to find, located in the object window. More precisely in winndow.location.search.

Therefore, if we request: www.first-contrib?query=react, what we get in the console is:

console.log(window.location.search); // "?query=react"

Ideally, rather than a string, it would be more convenient to manipulate a JS object properly formatted. To achieve that, instead of splitting the URL by = and ?, we'll use the URLSearchParams object, available in recent browsers. Otherwise, you can polyfill it thanks to this lib for instance.

With code, it yields to :

function getParams(location) {
  const searchParams = new URLSearchParams(location.search);
  return {
    query: searchParams.get('query') || '',
  };
}

therefore,

const params = getParams('www.first-contrib.fr?query=react');

console.log(params) // { query: "react" }

Now that we can get an object out of the URL, we'll make it work with our app which uses react-router. We'll therefore create a router which handles a route getting the properties in the URL as props.

import React from "react";
import { render } from "react-dom";
import { BrowserRouter as Router, Route } from "react-router-dom";

// ...
// getParams code above

//a simple component to display 
//the value of the query ...
// which is for now unknown
//so we'll instantiate it with an empty value
const MainPage = (props) => {
  let query = '';
  return (
    <h2>{`Query : ${query}`}</h2>
  );
}

const App = () => (
  <React.Fragment>
    <Router>
      <React.Fragment>
        <Route path="/" component={MainPage} />
      </React.Fragment>
    </Router>
  </React.Fragment>
);

render(<App />, document.getElementById("root"));

To get the actual value of query, we'll have to manipulate the function getParams that we wrote as well as the implicit props that MainPage receives from the Route object : <Route path="/" component={MainPage} />

If we logged that props, we'd get :

{match: Object, location: Object, history: Object, /*other stuff */}

What is of interest here is the location object similar to the window.location we manipulated earlier. Therefore, we can update the MainPage component to get the value inside the URL:

const MainPage = (props) => {
  const { location } = props;
  const { query } = getParams(location);

  return (
      <h2>{`My query: ${query}`}</h2>
  );
}

Now MainPage is plugged to the URL !

Update the URL (and the state) !

Now that we can read from the URL, we are going to implement a way to update the URL accordingly to the state of our app.

For that, a simple input will do:

class InputPage extends React.Component {

  state = { inputValue: "" };

  updateInputValue = e => this.setState({ inputValue: e.target.value });

  render() {
    return (
      <React.Fragment>
        <input
          type="text"
          placeholder="Change your URL !"
          value={this.state.inputValue}
          onChange={this.updateInputValue}
        />
        <input type="button" value="Change the URL" onClick={null} />
      </React.Fragment> 
    );
  }
}

So far, our component manage an internal state to display its current value but we still have to implement the onClick function to update the URL with that very same value.

We saw that the implicit props object from Route looks like that:

{match: Object, location:Object, history: Object, /*d'autres valeurs */}

What is of interest here is the history (additional information about history here...)

Thanks to its push function which according to React Router documentation :

Pushes a new entry onto the history stack

To say it simply, push will allow us to update the URL !

So if the query value in our input is javascript, we'll have to update our URL to the following value: www.myApp.io?query=javascript. We therefore need to generate the new searchParams of our URL. In order to do that URLSearchParams object will help us once again:

function setParams({ query = ""}) {
  const searchParams = new URLSearchParams();
  searchParams.set("query", query);
  return searchParams.toString();
}

Mind that without a default value for query when query is actually undefined, the generated URL would be ?query=undefined...

Now we can write :

const url = setParams({ query: "javascript" });
console.log(url); // "query=javascript"

We can then implement the onClick in he input component.

class InputPage extends React.Component {
  state = { inputValue: "" };
  updateInputValue = e => this.setState({ inputValue: e.target.value });

  updateURL = () => {
    const url = setParams({ query: this.state.inputValue });
    //do not forget the "?" !
    this.props.history.push(`?${url}`);
  };

  render() {
    return (
      <React.Fragment>
          <input
          type="text"
          className="input"
          placeholder="What am I looking for ?"
          value={this.state.inputValue}
          onChange={this.updateInputValue}
        />
        <input
          type="button"
          className="button"
          value="Update the URL !"
          onClick={this.updateURL}
        />
      </React.Fragment> 
    );
  }
}

Now if we change that value of the input, a click on the button we'll trigger the update of the URL and the MainPage will display the new value accordingly !

One of the nice thing that comes by having the state of your app in a URL is when you copy/paste link. Given that the state is included in this URL, we'll find the app in a specific state on first load !

When you deal with a search engine for instance, you can trigger the query as soon as the app is loaded. In this application, I use react-apollo but in naive way, we can implement the same thing with any HTTP client.

Let's create a component which triggers request using axios and the Github REST API (which does not require any authentication) as soon as it gets props using some of its lifecycle methods.


const httpClient = axios.create({
  baseURL: "https://api.github.com"
});

class ResultsPage extends React.Component {
  state = { results: [], loading: false, error: false };

  //Search as soon as it is mounted !!
  componentDidMount() {
    return this.searchRepositories(this.props.query);
  }

  //Search as soon as query value is updated
  componentWillReceiveProps(nextProps) {

    if (nextProps.query !== this.props.query) {
      this.setState({ query: nextProps.query });
      return this.searchRepositories(nextProps.query);
    }
  }

  searchRepositories = query => {

    //handle if query is undefined
    if (!query) {
      return this.setState({
        results: []
      });
    }

    this.setState({ loading: true, error: false });

    //the actual search on Github
    return httpClient
      .get(`/search/repositories?q=${query}`)
      .then(({ data }) =>
        this.setState({
          results: data.items,
          loading: false
        })
      )
      .catch(e => this.setState({ loading: false, error: true }));
  };


  render() {
    return (
      <div>
        {this.state.results.map(repo => (
          <div key={repo.id}>
            <a href={repo.html_url}>
              {repo.name}
            </a>
            <div>{`by ${repo.owner.login}`}</div>
          </div>
        ))}
      </div>
    );
  }
}

That's it! We now have a component which triggers request whenever the query params contained in the URL is updated !

As mentionned earlier, you can find a live example here.

In our example, we deal with only one searchParams but it becomes really cool and powerful if more components can modify the URL. For instance, pagination, filtering, sorting, etc can become parameters of the URL. It could then look like that: https://myApp.io?query=react&sort=ASC&filter=issues&page=2.

The code would be similar as what we did previously. By modifying the URL, implicit props provided by the Route component are updated. It then triggers a rerender and update all the children listening to a specific value in the URL. Therefore it leads to UI update(s) or side effect(s) such as an HTTP call.

Conclusion

That's it ! This article was an attempt to show that there are still alternatives to handle the global state of a React App that can be very light in terms of bundle size (0kb in modern browser ><) ans still fun, simple and providing for free a (kind of) deep linking effect which I find very cool :)

Hope you enjoy !

A Github's search engine for OSS contributors wannabe

GaelS — Tue, 15 May 2018 07:57:38 +0000

TLDR: it's live here and the code is here

Hi all,

It can be hard sometimes for beginners to find THE good project and THE good issue to make a first open source contribution. In order to tackle, I created an application powered by the Github's GraphQL API.

It works as a search engine which allows you to query by keywords and languages across all repositories to find issues tagged with beginners friendly labels (I have listed more than 50 of them so far!).

The Github's API does not really expect this kind of use case where you want to search across all repositories. So, tweaks and workarounds had to (and some still need to) be found to handle in a better way some features such as the pagination for instance.

Besides, to have fun while practicing my CSS skills, I tried to achieve a 80's vibes design, hope you'll like it or better, will want to improve it !

This app is realized with React (preact under the hood), React Router and React Apollo.

Feel free to give me your feedbacks whether you like it or not :)

Thanks,
Gaël

PS : A small preview below :)

DEV Community: GaelS