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

thrutab

v0.0.2

Published

Simple data exchange between tabs with the same origin

Downloads

4

Readme

ThruTab

This module is designed to simplify communication between tabs in the browser, for example to avoid loading some information twice, or to synchronize the results of your requests in time. In real-world tasks it is very useful to combine with Redux storage, but nobody can forbid you to use it for localStorage.

Works on Vanilla, React Hooks, Vue 3 (testing)!

This module has an exposed callback, which will need to be added to a message event in the Service Worker So Service Worker is required!

Basic Usage

There's a list of basic functions:

Usage with frameworks:

React

Implementations

getTypedSwTunnel()

Used in Service Worker

// Returns Typed SW Tunnel for managing messages
getTypedSwTunnel() 

// Usage in service-worker.ts
self.addEventListener('message', getTypedSwTunnel<any>())
// NOTE: self is ServiceWorkerGlobalScope

manageSubscription()

Used in Service Worker registration

// Will add your signature to SW Tunnel clientStore
manageSubscription(ONLOAD_GENERATED_SIGNATURE)

// Somewhere in registration Service Worker with Workbox Window
// For example you can use this in your index.tsx
...
const localSign = crypto.randomBytes(10).toString('hex')

wb.register()
.then((reg) => {
  manageSubscription(localSign)
})
...

requestData()

// Request key someKey in other tabs
requestData({
    requestKey:'someKey', 
    timeout: CUSTOM_TIMEOUT_IN_MS
    })
  .then((result) => {
    setData(result)
  })
  .catch((e) => console.log('Rejected by timeout, probably', e))
  

syncData()

// Patch someKey value in all tabs (besides the current)
syncData('someKey', cachedData)

registerHandler()

Used in a module that has access to the cache (for example with @redux/toolkit) See also in React.js section

const handleRequests: RequestHandlerFn = useCallback(
(data, reply, reject) => {
  console.log('Got to handle', data)
  if (data && Object(cache).hasOwnProperty(data.requestKey)) {
    console.log('request is going to be fulfilled')
    reply(cache[data.requestKey].data)
  } else {
    reject()
  }
},
[cache],
)

const handleSync: SyncHandlerFn = useCallback(
(data) => {
  dispatch(
    save({
      key: data.key,
      data: data.data,
    }),
  )
},
[dispatch],
)

const handlersRef = registerHandler(handleRequests, handleSync)

...

// Do not forget to unregister handler before page closes
unregisterHandler(handlersRef)

unregisterHandler()

Check last lines of the previous section

As React Hooks

useConnectorFn(requestHandler, syncHandler)

const handleRequests: RequestHandlerFn = useCallback(
(data, reply, reject) => {
  console.log('Got to handle', data)
  if (data && Object(cache).hasOwnProperty(data.requestKey)) {
    console.log('request is going to be fulfilled')
    reply(cache[data.requestKey].data)
  } else {
    reject()
  }
},
[cache],
)

const handleSync: SyncHandlerFn = useCallback(
(data) => {
  dispatch(
    save({
      key: data.key,
      data: data.data,
    }),
  )
},
[dispatch],
)

useConnectorFn(handleRequests, handleSync)

useSharedData()

const { requestData, syncData } = useSharedData()

// Request key someKey in other tabs
requestData('someKey', CUSTOM_TIMEOUT_IN_MS)
  .then((result) => {
    setData(result)
  })
  .catch((e) => console.log('Rejected by timeout, probably', e))
  
// Patch someKey value in all tabs (besides the current)
syncData('someKey', cachedData)