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-root

v1.4.0

Published

Units in the root domain for testing and SSR support

Downloads

13,811

Readme

effector-root

Commitizen friendly Conventional Commits code style: prettier

Do not depend on this package in your libraries!

Motivation

Sometimes we developed our apps and just afterwards start thinking about SSR and testing. For these purposes any effector app need to have root domain. Usually we just manually update declarations. For example, from createEvent to rootDomain.createEvent. It takes time. effector-root provides you the possibility to have all units attached to the root domain without any manual actions.

Usage

  1. Replace all imports of effector to effector-root. You can do it by yourself or with babel plugin

  2. To retrieve our app root domain we need just to import it.

import { root, createEvent, attach, fork } from 'effector-root';

Create React App and macros support

Replace all imports of effector to effector-root/macro to automatically add sid:

import { root, createEvent, attach, fork } from 'effector-root/macro';

Note: babel-plugin-macros do not support import * as name, so Your import import * as effector from 'effector-root/macro won't work

Compat

You can easily use effector/compat in your application with effector-root, just:

import { root, createEvent, attach, fork } from 'effector-root/compat';

Note: root domain from effector-root/compat is not the same domain as from effector-root

How to auto replace all imports of effector to effector-root using babel plugin

  1. Install babel-plugin-module-resolver
  2. Add to plugins:
['module-resolver', { alias: { effector: 'effector-root' } } ]