Scott Mikula
Scott Mikula
The primary purpose of Satchel is as a state management library: actions are dispatched and handled by mutators in order to modify the store. Once we have this publish-subscribe pattern...
Mutators are meant to *respond* to actions, but not to dispatch further actions. Within modern Satchel this is enforced, but it's currently possible to call a legacy Satchel action from...
# Preface Satchel exists because, while we liked the Flux pattern and Redux in particular, there were a few things we wanted that Redux couldn't give us. * **Strong typing...
This implements most of #97 -- please see that issue for details. (I didn't implement the `nullOn` or `definedOn` APIs yet since it's not clear how much value they would...
## Description OpenDominion looks _great_ on a phone, but it looks pretty terrible in a web browser on my widescreen monitor.  ## Possible Fix Provide a maxwidth to the...
Currently if you have a rule like: ```json "dependencies": [ "core-js" ] ``` ...we only allow imports of `corejs` specifically, not something like `corejs/lib/whatever`. It can be confusing to get...
It would be great to have VSCode integration so you can see fences errors at dev time.
The rules in fence.json use the same resolve logic as module resolution: file extensions are omitted. But it's really easy to make a mistake and accidentally include them. E.g.: ```json...
Currently there is one for deriving the bundle data (`assetFilter`) and two for generating the report (`chunkGroups` and `moduleNameTransform`).
When doing some debugging in a related area, I noticed this error happening within `react-shadow`: ``` Failed to execute 'attachShadow' on 'Element': Shadow root cannot be created on a host...