npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

query-to-extension

v1.0.2

Published

Plugin that connects react-query to chrome extension service worker

Downloads

2

Readme

query-to-extension

Plugin that connects react-query to chrome extension service worker.

Current version stills in beta, use at your own risk.

Typing still needs to be well implemented.

file that runs in your popup, pages or scripts

Connect your react-query instance (Queryclient) to the extension service worker listeners.

// queryClient.ts
import { QueryClient } from "@tanstack/react-query";
import { connectContextToExtension } from "query-to-extension";

const queryClient = new QueryClient(/* ... */);

connectContextToExtension(queryClient, {
  // here you can define your own connection name
  connectionName: "chrome-extension-boilerplate-script",
});

export default queryClient;

file that runs in your service worker

Register queries in your service worker runtime, using chrome extension api. Sets an arrangement of listeners for each described query and one for mutations, data sent to listeners, will return back as a query value.

// service-wroker.ts
import { registerQueriesMap } from "query-to-extension";

import { QUERY_COUNTER, QUERY_DATA } from "../queryIds";

// receives message from interface and delivery it back directly to query `data`;
/* (context: MappedQueryListenerMessage) => Promise<any> */
import serviceData from "./serviceData";
import serviceCounter from "./serviceCounter";

// receives the same data as mutation receives as message directly from interface and delivery
// it back to mutation function;
/* (context: any) => Promise<any> */
import mutationFn from "./mutationFn";

type MyQueryMap = Parameters<typeof registerQueriesMap>[0];

// you can pass the necessary mutation response type
type MutationResponseType = {
  /* ... */
};

const queriesMap = [
  {
    queryKey: QUERY_DATA,
    listenerFn: serviceData,
    broadcast: true,
  },
  {
    queryKey: QUERY_COUNTER,
    listenerFn: serviceCounter,
    broadcast: true,
  },
  /* ... */
] as MyQueryMap;

registerQueriesMap<MutationResponseType>(queriesMap, mutationFn);

Component implementation:

Your component imlplementation is even simpler, all query fucntion complexity now goes to the service worker runtime and you don't need to worry about it in the component.

/* ... rest of your component ... */

const queryData = useQuery({
  queryKey: [...QUERY_DATA, { from: "popup" }],
  initialData: -1,
  // no query function is necessary here, service worker listener will replace it
});

/* ... rest of your component ... */