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

effector-inspector

v0.14.1

Published

| Dark theme and unit tracing | Units in files | | ----------------------------------------------- | ----------------------------------------- | | ![Dark-Traces](https://i.imgur.com/m9arc8u.png) | ![Units](ht

Downloads

28,058

Readme

Effector Inspector

| Dark theme and unit tracing | Units in files | | ----------------------------------------------- | ----------------------------------------- | | Dark-Traces | Units |

Installation

Standalone

  1. Install effector-inspector
npm install --dev effector-inspector

or

yarn add -D effector-inspector
  1. Make sure, that you have either effector/babel-plugin or @effector/swc-plugin set up in your project. These plugins add metadata to all effector's units, which is then used by effector-inspector.

Check out the documentation of effector/babel-plugin or @effector/swc-plugin.

  1. Initialize inspector in your application's entrypoint (something like index.ts or client.tsx).
import {createInspector} from 'effector-inspector';

createInspector();
  1. After that inspector is ready to work, but it does not know about any units yet. You also need to attach inspector to units.

One way to do it is to attach inspector to units manually:

import {attachInspector} from 'effector-inspector';

// single units
attachInspector($store);
attachInspector(event);
attachInspector(effectFx);
// or list of them
attachInspector([
  $store,
  event,
  effectFx,
  // any number of units in the list
]);
// or by domain
attachInspector(someDomain);

effector-root

The effector-root library can be used for convenience, as it provides common root domain for all units.

// index.ts
import {attachInspector, createInspector} from 'effector-inspector';
import {root} from 'effector-root';

createInspector();
attachInspector(root);

Check out effector-root documentation here.

As a part of effector-logger

  1. Install effector, logger and inspector
npm install effector
npm install --dev effector-logger effector-inspector

or yarn

yarn add effector
yarn add -D effector-logger effector-inspector
  1. Follow instructions for effector-logger
  • Setup babel plugin
  • Replace effector to effector-logger
  1. Open your root application file (something like client.tsx or index.tsx)

Initialize effector logger in it first lines.

import {createInspector} from 'effector-inspector';

createInspector();
  1. Press hot keys to open inspector

By default: CTRL+B in your application

  1. Watch your stores and its values

Release process

  1. Check out the draft release.
  2. All PRs should have correct labels and useful titles. You can review available labels here.
  3. Update labels for PRs and titles, next manually run the release drafter action to regenerate the draft release.
  4. Review the new version and press "Publish"
  5. If required check "Create discussion for this release"