Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
reactive-box
Advanced tools
Minimalistic, fast, and highly efficient reactivity.
Hi friends! Today I will tell you how I came to this.
Redux has so many different functions, Mobx has mutable objects by default, Angular so heavy, Vue so strange, and other them so young :sweat_smile:
These funny thoughts served as fuel for writing the minimal reaction core. So that everyone can make their own syntax for managing the state of the application in less than 100 lines of code :+1:
It only three functions:
box
- is the container for an immutable value.sel
- is the cached selector (or computed value) who will mark for recalculating If some of read inside boxes or selectors changed.expr
- is the expression who detects all boxes and selectors read inside and reacted If some of them changed.import { box, sel, expr } from "reactive-box";
const [get, set] = box(0);
const [next] = sel(() => get() + 1);
const [run, stop] = expr(
() => `Counter: ${get()} (next value: ${next()})`,
() => console.log(run())
);
console.log(run()); // console: "Counter 0 (next value: 1)"
set(get() + 1); // console: "Counter 1 (next value: 2)"
It is a basis for full feature reactive mathematic! For example that possible syntax to transcript previous javascript code:
a` = 0 // create reactive value
next` = a` + 1 // create new reactive value, dependent on the previous one
expr = { "Counter: ${a`} (next value: ${next`})" } // create reactive expression
// subscribe to expression dependencies were change and run It again
expr: () => console.log(expr())
// run the expression
console.log(expr()) // message to console "Counter: 0 (next value: 1)"
a` = a` + 1 // here will be fired log to console again with new "Counter: 1 (next value: 2)" message, because a` was changed.
a
a + 1
"Counter: ${a} (next value: ${next})"
a
and next
reactive dependenciesa
for demonstration subscriber reactionThese are three basic elements necessary for creating data flow any difficulty.
The first element is a reactive container for an immutable value. All reactions beginning from container change value reaction.
The second one is the middle element. It uses all reactive containers as a source of values and returns the result of the expression. It's a transformer set of reactive values to a single one. The selector can be used as a reactive container in other selectors and expressions. It subscribes to change in any of the dependencies. And will recalculate the value if some of the dependency changed, but will propagate changes only if the return value changed.
And the last one is a reaction subscriber. It provides the possibility to subscribe to change any set of reactive containers. It can be run again after the listener was called.
It runs calculations synchronously.
glitch free - your reactions will only be called when there is a consistent state for them to run on.
Possibility for modification everywhere: in expressions and selectors!
Below we will talk about more high level abstraction, to the world of React and integration reactive-box into, for best possibilities together!
Basic usage examples:
It is minimal core for a big family of state managers' syntax. You can use the different syntax of your data flow on one big project, but the single core of your reactions provides the possibility for easy synchronization between them.
import React from "react";
import { computed, immutable, observe, shared } from "./core";
class Counter {
@immutable value = 0;
@computed get next() {
return this.value + 1;
}
increment = () => this.value += 1;
decrement = () => this.value -= 1;
}
const App = observe(() => {
const { value, next, increment, decrement } = shared(Counter);
return (
<p>
Counter: {value} (next value: {next})
<br />
<button onClick={decrement}>Prev</button>
<button onClick={increment}>Next</button>
</p>
);
});
import React from "react";
import { action, store, selector, useState } from "./core";
const increment = action();
const decrement = action();
const counter = store(0)
.on(increment, (state) => state + 1)
.on(decrement, (state) => state - 1);
const next = selector(() => counter.get() + 1);
const App = () => {
const value = useState(counter);
const nextValue = useState(next);
return (
<p>
Counter: {value} (next value: {nextValue})
<br />
<button onClick={decrement}>Prev</button>
<button onClick={increment}>Next</button>
</p>
);
}
You can easily make your own state manager system or another observable and reactive data flow. It's so funny :blush:
npm i reactive-box
Thanks for your time!
FAQs
Minimalistic, fast, and highly efficient reactivity
The npm package reactive-box receives a total of 82 weekly downloads. As such, reactive-box popularity was classified as not popular.
We found that reactive-box demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.