effector-inspector
v0.14.1
Published
| Dark theme and unit tracing | Units in files | | ----------------------------------------------- | ----------------------------------------- | |  | .
import {createInspector} from 'effector-inspector';
createInspector();- 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
- Install effector, logger and inspector
npm install effector
npm install --dev effector-logger effector-inspectoror yarn
yarn add effector
yarn add -D effector-logger effector-inspector- Follow instructions for effector-logger
- Setup babel plugin
- Replace
effectortoeffector-logger
- Open your root application file (something like
client.tsxorindex.tsx)
Initialize effector logger in it first lines.
import {createInspector} from 'effector-inspector';
createInspector();- Press hot keys to open inspector
By default: CTRL+B in your application
- Watch your stores and its values
Release process
- Check out the draft release.
- All PRs should have correct labels and useful titles. You can review available labels here.
- Update labels for PRs and titles, next manually run the release drafter action to regenerate the draft release.
- Review the new version and press "Publish"
- If required check "Create discussion for this release"
