Sam Richard

This happens when I use an Element outside of a Frame. The default value for `NodeContext` is `null` - which has an attempt to unpack it in `useInternalNode`: ```js const...

I may be conflating two problems. I was getting this react warning in my own code: > warning.js:33 Warning: Can't call setState (or forceUpdate) on an unmounted component. This is...

Like you said, it looks like this happens in the constructor: https://github.com/drcmda/react-contextual/blob/master/src/store.js#L65 The Provider specific actions are `Object.assigned` to the store state. So they are persisted. AFAIK, this is unwanted?...

This still puts Provider bound actions in the external store, they just will not stack (see the example with both Containers shown). I'm working on a PR that does a...

As far as motivation, i don't want to always provide the store, as I may never need it unless a page loads it. The trigger for needing to load it...

@drcmda I started looking at [unstated](https://github.com/jamiebuilds/unstated) after it got a bit popular. It has a bit of overlap with your library's stores, but it doesn't provide the context manipulation that...

@drcmda I already use `transformContext` in our code base - I don't know why I never thought of some of our side effects as derived state. I'll have to spend...

Old Examples: Something to do with middleware ``` export const AuthStore = createStore({ user: null, setUser: user => ({ user }) }) ... // Logging AuthStore.subscribeActions((payload, action) => { console.log(`received...

@drcmda I went ahead and set this up to not make too much public API. Providers now have a subscription to their store and will re-render according to ordinary `setState`...

@drcmda I'm not sure what else I should be contributing. I detail a lot since I feel like I'm stepping on the toes of a "less than 1kb" opinionated library....