Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/effector/logger/releases below:

Releases · effector/logger · GitHub

Releases · effector/logger

effector-logger is re-written to use brand new Inspect API of effector. Root domain setups, custom babel-plugins and etc are no longer needed.

Simple attachLogger() call somewhere in your app entrypoint is enough now.

Also effector-logger now only does console logs and Redux DevTools support and effector-inspector integrations are removed. Use @effector/redux-devtools-adapter and effector-inspector instead.

• Redux DevTools support and effector-inspector integrations are removed. Use @effector/redux-devtools-adapter and effector-inspector instead.
• effector-logger/attach is removed. Use main attachLogger export instead. Notice, that config shape is different and does not require root domain now.
• effector-logger/babel-plugin is removed. It is no longer needed, just use effector/babel-plugin or @effector/swc-plugin normally.
• import { createEvent, ... } from "effector-logger" support is removed. Use patronum/debug from patronum.effector.dev instead if you need to log only some units.
• Babel Macro support is removed. Create-React-App is basically deprecated at this point. Use something else (e.g. Vite) instead.

• configure now supports log: 'enabled' option to forcefully log some unit that is usually omitted. It is useful to log updates of derived units which are omitted by effector-logger by default.
• effector Scope logs are fully supported now, domain is not required
• You can provide name prefix to your logs if needed. It can be useful in case if there are few instances of your app which are using different scopes.

Old integration tests are removed. Now there is a single suit of vitest-based tests which is run against dist output of the library bundler.

1. Remove effector-logger/babel-plugin if it was used. Use effector/babel-plugin or @effector/swc-plugin instead.
2. Remove any effector -> effector-logger build-time aliases if you had used them.
3. Remove all import { createEvent, createStore, ... } from "effector-logger" imports. Use imports from effector instead. In case if you need to see only specific units in the logs - use patronum/debug instead
4. Remove any effector-logger/macro imports, if you had used them.
5. Remove any effector-logger/attach imports.
6. Update effector to version 22.8.3

If you have used effector-logger for Redux DevTools integration - use @effector/redux-devtools-adapter instead.

If you have used effector-logger for effector-inspector integration - use effector-inspector directly.

Just add import { attachLogger } from "effector-logger" at the top of your app's entrypoint module and call attachLogger() (or attachLogger({ scope }) if your app uses scope) somewhere in the entrypoint module.
See updated README.md for details.

• Use Inspect-API instead of root domain setup #119 (@AlexandrHoroshih)

• Use Inspect-API instead of root domain setup #119 (@AlexandrHoroshih)
• Fix typos and improve code highlighting on README.md #118 (@terechshenkov)

• Add guide for non-babel users #90 (@YanLobat)

• Fixed issue with not exported types (#115)

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4