In a sense, some of it could be adapted, but with relaxing the idea of "components are pure functionsnindependant of a base" to "components are pure functions p

In a sense, some of it could be adapted, but with relaxing the idea of "components are pure functionsnindependant of a base" to "components are pure functions producing data usable by a given base using a given UI framework". For example, in a react / redux app, you would have "pure" components representing the business logic of your app, either a component or a base that actually stuff them in a redux store ; a multiple "react-components" that returns jsx ; and at least one "react base" (or react/redux base) that ties everything. Different projects would be "your real application", "your dev server connected to local stub services", "your storybook execution", etc...