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

@respite/exchange

v4.0.0

Published

> TODO: description

Downloads

81

Readme

@respite/exchange

This is a very small library that lets you to link your respite actions and queries in an agnostic location in your code base.

For some context: right now if you have an action that updates your data on the back end, you have to then manually invalidate your queries as part of the action:

return useAction(async () => {
  const result = await doSomeMutating();

  myQuery.invalidate();

  return result;
})

or invalidate a whole collection of queries:

const action = useAction(async () => {
  const result = await doSomeMutating();

  action.invalidate({ key: 'myQuery' });

  return result;
});

return action;

The problem with this is that a) you have to break out of your mutating process to clear your queries, and then return to the mutating again, and b) you're tightly coupling your actions to your queries. Sometimes you don't even know what queries are depending on the data you've just updated!

@respite/exchange offers a way for you to declare which queries are invalidated by which actions, separate to the actions themselves.

With exchange, your action would look like this:

return useAction('my-action', doSomeMutating);

and then, separately, you would link your actions and queries like this:

useExchange([ 'myQuery', 'my-action' ]);

Now whenever your action is triggered, the query will be invalidated, but neither action nor query are coupled!

You can pass in multiple actions and multiple queries, it's entirely up to you how you want to organise your exchanges:

useExchange(
  [ 'myQuery', [ 'update', 'create', 'delete' ] ],
  [ ['authQuery', 'userQuery' ], 'updateUser' ],
  [ [ 'basketQuery', 'voucherQuery' ], [ 'updateBasket', 'applyVoucher' ] ],
);