Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
@solid-primitives/rootless
Advanced tools
A collection of helpers that aim to simplify using reactive primitives outside of reactive roots, and managing disposal of reactive roots.
A collection of helpers that aim to simplify using reactive primitives outside of reactive roots, and managing disposal of reactive roots.
createBranch
- Creates a reactive root branch, that will be automatically disposed when it's owner does.createCallback
- A wrapper for creating callbacks with runWithOwner
.createDisposable
- For disposing computations early – before the root cleanup.createSharedRoot
- Share "global primitives" across multiple reactive scopes.npm install @solid-primitives/rootless
# or
yarn add @solid-primitives/rootless
createBranch
createSubRoot
Creates a reactive root branch, that will be automatically disposed when it's owner does.
Use it for nested roots (literally nested, or provided manually to dependency array) that should be disposed before or with their owner.
import { createBranch } from "@solid-primitives/rootless";
createRoot(dispose => {
createBranch(disposeBranch => {
// computations will be disposed with branch
createEffect(() => {...});
// disposes only the branch
disposeBranch();
});
// disposes the outer root, AND all the nested branches
dispose();
});
function createBranch<T>(fn: (dispose: VoidFunction) => T, ...owners: (Owner | null)[]): T;
createCallback
A wrapper for creating callbacks with runWithOwner
.
It gives you the option to use reactive primitives after root setup and outside of effects.
Why?
All of the callback-based (in opposite to effect-based) events is Solid don't have a root, because the root is changed synchronously after initialization finishes. So normally that would prevent you from using reactive primitives there.
runWithOwner
attatches whatever computations created inside, to the owner passed to it.
// in component body
const handleClick = createCallback(() => {
// the effect will be created normally, attached to the component's reactive root
createEffect(() => {...})
})
// in jsx
<button onClick={handleClick} />
function createCallback<T extends AnyFunction>(callback: T, owner?: Owner | null): T;
createDisposable
runWithSubRoot
For disposing computations early – before the root cleanup.
Executes provided function in a createBranch
(auto-disposing root), and returns a dispose function, to dispose computations used inside before automatic cleanup.
const dispose = createDisposable(dispose => {
createEffect(() => {...})
});
// dispose later (if not, will dispose automatically)
dispose()
type runWithRootReturn<T> = T extends void | undefined | null
? Dispose
: [returns: T, dispose: Dispose];
const createDisposable = <T>(fn: () => T, detachedOwner?: Owner): runWithRootReturn<T>
createSharedRoot
@1.1.0
Creates a reactive root that is shared across every instance it was used in. Shared root gets created when the returned function gets first called, and disposed when last reactive context listening to it gets disposed. Only to be recreated again when a new listener appears.
Designed to make "global primitives" shareable, without instanciating them (recreating, state, computations, event listeners, etc.) every time they're used. For example a createLocationState
primitive would work the same for every instance and provide the same data, so reinitializeing it every time is wastefull.
createSharedRoot
primitive takes a single argument:
factory
- a function where can you initialize some reactive primitives, returned value will be shared across instances.And returns a function registering reactive owner as one of the listeners, returns the value factory
function returned.
import { createSharedRoot } from "@solid-primitives/rootless";
const useState = createSharedRoot(() => {
return createMemo(() => {...})
});
// later in a component:
const state = useState();
state()
// in another component
// previously created primitive would get reused
const state = useState();
...
function createSharedRoot<T>(factory: (dispose: Fn) => T): () => T;
Usage of combining createSharedRoot
with createMousePosition
: https://codesandbox.io/s/shared-root-demo-fjl1l9?file=/index.tsx
0.0.100
Initial release as a Stage-1 primitive.
1.0.0 - Stage-2
Remove runWithRoot
Rename createSubRoot
to createBranch
and runWithSubRoot
to createDisposable
(also unify returns to only dispose fn)
1.1.0
Add createSharedRoot
primitive
FAQs
A collection of helpers that aim to simplify using reactive primitives outside of reactive roots, and managing disposal of reactive roots.
The npm package @solid-primitives/rootless receives a total of 18,497 weekly downloads. As such, @solid-primitives/rootless popularity was classified as popular.
We found that @solid-primitives/rootless demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers 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
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.