Sova

@bakugod Can you reproduce the bug in stackblitz/codesandbox on some bundler (for ex. vite)?

You can use `combine` ```ts split({ clock: handleSendMessage, source: combine([$editingMessage, $messageInputFieldText]), // ... }) ```

> How can I suppress this message? ```ts $user.on(handlePushTokenChangeFx.doneData, (user, result) => { if (user && result?.pushToken) { return { ...user, pushToken: result.pushToken, }; } // just return the same...

I suppose we don't need to rename the whole hook: ```ts const value = useStoreMap({ source: { a: $a, b: $b, c: $c }, // Just rename the parameter. Or...

You need to return `null` instead of `undefined` from the `fn`. ```ts const selectedUser = useStoreMap({ store: $users, keys: [selectedUserId], fn: (users, [selectedUserId]) => users.find((user) => user.id === selectedUserId) ??...

We need to add more information about this behavior to the docs. But you can refer this article https://effector.dev/docs/api/effector/store/#formulae-1

All tools like Babel and SWC work on the File-level, not the project level. When you process a factory call you have just the import statement, and the call itself....

Maybe sort items by usage? ```rust fn foo() { bar(); baz(); } fn baz() { println!("World!"); } fn bar() { gah(); } fn gah() { println!("Hello"); } ``` After sort:...

> I would suggest something simpler, like just to expose internal effects of timer-based operators, like this: > > ```ts > const scope = fork({ > handlers: [ > [debounce.timerFx,...

I recommend to transpile your node_modules for target browsers. Because optional chaining is enabled for two years already: