Last 12 weeks · 0 commits
2 of 6 standards met
Repository: developit/unistore. Description: 🌶 350b / 650b state container with component actions for Preact & React Stars: 2852, Forks: 137. Primary language: JavaScript. Languages: JavaScript (100%). Homepage: https://npm.im/unistore Topics: architecture, preact, redux, state, subscription, unistore. Latest release: 3.5.2 (5y ago). Open PRs: 10, open issues: 36. Last activity: 4y ago. Community health: 42%. Top contributors: developit, namankheterpal, vincentaudebert, heldr, kokjinsam, eduardoborges, marvinhagemeister, kadmil, SolarLiner, goblindegook and others.
JavaScript
Admittedly I can't run the tests on my Windows machine :( So take this PR with a grain of salt. npm-run-all --silent -p build:main build:integrations build:combined -s size docs Error: ENOENT: no such file or directory, open 'D:\dev\projects\unistore\src\integrations\.js' Error: ENOENT: no such file or directory, open 'D:\dev\projects\unistore\src\combined\.js' Build output to dist: 554 B: unistore.es.js 323 B: unistore.js 391 B: unistore.umd.js 325 B ERROR There is no matching file for full/preact.js in D:\dev\projects\unistore Cheers
It doesn't seem I can easily edit or fork the referenced benchmark, but in the latest Chrome (78), this appears to perform slightly better than the current implementation: !image Benchmark details Setup: ``` const store7 = createStore(); let viaPreallocated = (function viaPreallocated(store, action) { return function() { let args = new Array(arguments.length + 1); args[0] = store.getState(); for (let i=0; i It's a technique we use in our state library's selector binding. The size bump is bigger than expected, not significant, but enough to fail tests without adjusting the permitted bundle size.