store .manage() resources

[jbolda]

Motivation

Pulled out the .manage() API from #67. We could still iterate on #67 a bit, but the resource handling is likely ready to move forward.

[pkg-pr-new]

More templates

• basic-react
• parcel-react
• tests-rtl
• vite-react

npm i https://pkg.pr.new/fxforge/starfx@77

commit: 6ffcc4b

[jbolda]

@neurosnap I added an effection resource doc, but didn't link it anywhere. Recommendations how/where we might include this in the narrative?

[neurosnap]

Would you consider this advanced usage?

[jbolda]

Hmm at the current time I might? You could, for example, grab the @effectionx/worker package though, drop it in here, and just start using it. The DX and ease of use can be relatively inviting though. I suspect that not everyone will need this, and if you would, you could likely be looking for it. As such, advanced usage section feels reasonable.

[jbolda]

I added it as a section under the guides for now unless you have a better idea, @neurosnap.

[neurosnap]

Hmm, help me understand why this should live within our store which mostly deals with our single global object. If I were designing this API I would probably keep it at the thunk level. Is the problem that we need to share the same instance of an object across all thunks?

[jbolda]

That would be the specific use case, yes. So you could opt to "share" it at a specific thunk level via thunk.manage or make it "globally" available at store.manage. We effectively have these two "levels" where we could establish context, and it feels useful to enable at both.

[jbolda]

It is not immediately clear why slice is undefined in that test. Will want to clear that up before we move forward here.