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 🙏

© 2026 – Pkg Stats / Ryan Hefner

expo-redux-logger

v2.0.0

Published

redux logger for Expo project

Readme

Redux Logger for Expo

  • super simple redux logger specifically designed for Expo projects
  • the main advantage of using this logger over other redux loggers, is it allows you to separate your redux logs from your other logs

screenshot

Why Use this Package?

  • separate your redux logs from other logs when remote debugging
  • prevent your console from being overrun with redux logs!

Install

`npm i expo-redux-logger

Basic Usage

First, enable remote debugging when you are running your Expo project. If you don't know how see 'How To Enable Remote Debugging With Chrome' section below. Now, when your redux state changes, you will see those logs in the remote console, but your terminal will only display your non-redux console.log statements. This makes it much easier to find logs you are looking for without having to entirely remove logging middleware.

import { applyMiddleware, createStore } from "redux";
import { expoLogger } from "expo-redux-logger";

const store = createStore(reducer, applyMiddleware(expoLogger));

Helpful iOS Simulator Shortcuts for mac

This isn't specific to this package, but I thought I would include these shortcuts because sometimes enabling remote debugging causes some strange errors when using expo and you just need to restart it.

  • normal restart - cmd+ctrl+z to reveal dev menu, then press Reload
  • if normal restart isn't working - press shitf+ctrl+cmd+h to open app-switcher, swipe up to close expo app, re-open expo app

How To Enable Remote Debugging With Chrome

This package also works with the normal React-Native remote debugger as long as your project is managed by Expo https://docs.expo.io/workflow/debugging/

You can debug Expo apps using the Chrome debugger tools. Rather than running your app's JavaScript on your phone, it will instead run it inside of a webworker in Chrome. You can then set breakpoints, inspect variables, execute code, etc, as you would when debugging a web app.

To ensure the best debugging experience, first change your host type in Expo Dev Tools to LAN or localhost. If you use Tunnel with debugging enabled, you are likely to experience so much latency that your app is unusable. While here, also ensure that Development Mode is checked.

If you are using LAN, make sure your device is on the same wifi network as your development machine. This may not work on some public networks. localhost will not work for iOS unless you are in the simulator, and it only work on Android if your device is connected to your machine via usb.

Open the app on your device, reveal the developer menu (cmd+ctrl+z for iOS simulator) then tap on Debug JS Remotely. This should open up a Chrome tab with the URL http://localhost:19000/debugger-ui. From there, you can set breakpoints and interact through the JavaScript console. Shake the device and stop Chrome debugging when you're done.

Line numbers for console.log statements don't work by default when using Chrome debugging. To get correct line numbers open up the Chrome Dev Tools settings, go to the "Blackboxing" tab, make sure that "Blackbox content scripts" is checked, and add expo/build/logs/RemoteConsole.js as a pattern with "Blackbox" selected.

License

MIT