Package structure

[ghengeveld]

We should settle on a general direction for package structure and naming. This issue is not for discussing package details, but to discuss where to cut them up or merge them. Refer to packages/react-async/src for an overview of what's currently there. The goal is to offer a way to later add new features without affecting the existing functionality, by using separate packages.

Current idea:

• @async-library/core Core features, library agnostic: reducer, status, globalScope
• @async-library/devtools Chrome DevTools extension, supports all libraries
• @async-library/react-async-component React Component with Render Props API (<Async>) and its helper subcomponents (aka classic React Async)
• @async-library/react-async-hook React Hook (useAsync) and standalone helpers
• @async-library/react-fetch-hook React Hook (useFetch), depends on react-async-hook
• @async-library/vue-async-composition Vue.js Composition, following the Vue Composition API

Questions:

• How do we deal with propTypes? Do they go in core somehow? Can we generate them from TypeScript?

[AlbertBrand]

Sounds like a proper split, although @async-library seems a bit long. Also, vue-fetch-composition can be split off from the Vue parts.

For getting cross lib props right I would generate them, probably from a typed model (TS seems fine for this). A description in JSON would suffice as source model as well.