Should make same change that happened in #13 to ReduxularElement to Reduxular itself.
Caused by #12

Include process polyfill automatically (needed for redux).

Once it is working in multiple projects, add some amazing tests

When I have a typescript project that depends on this through npm and then I try to use tsc to transpile my project it fails with several errors from reduxular. Excluding node_modules doesn't help neither does adding "skipLibCheck": true to compilerOptions in tsconfig.json.

I suggest that the published package includes only already-transpiled (.js) files and include the type definitions.

Once it is working in multiple projects, add an amazing README.

The types are really good right now, but we have a few any's laying around. Get rid of them and make the types perfect

Just throw createObjectStore into the constructor.

Right now there is no official way to get to the generated root reducer when using createObjectStore. We can provide a custom reducer that is combined with the root reducer, but we can't get to the root reducer itself. My use case for this is performing tasks after the state has been updated, for example persisting the entire state to local storage. I can do it in a listener, but it might be nice to create reducer that encapsulates this functionality, a pattern I've used elsewhere

It's becoming common for me to create a special action called RESET_STATE just to set the state back to the InitialState inside of a component. I would love a property called state that would simply do this for me. And that would be nice

Once it is working in multiple projects, write an amazing article and spread the word

If the state type generic contains an optional property and that property is correctly omitted from the initial state in the constructor, the property never gets set afterwards even when consumers attempt to do so.

Example component:

import {html, render as litRender} from 'lit-html';
import {ReduxularElement} from '../../reduxular-element';

type State = {
    // NOTE: this is optional!
    optionalCount?: number;
};

// This initial state is valid!
const initialState: Readonly<State> = {};

class ReduxularElementTestOptionalProperty extends ReduxularElement<State> {
    constructor() {
        super(initialState, state => {
            litRender(this.render(state), this);
        });
    }

    render(state: Readonly<State>) {
        console.log('reduxular-element-test-optional-property:', state.optionalCount);

        return html`
            <div>reduxular-element-test-optional-property: ${state.optionalCount}</div>
        `;
    }
}

window.customElements.define('reduxular-element-test-optional-property', ReduxularElementTestOptionalProperty);

To see in action add the following to reduxular-app.ts's render method output:

<reduxular-element-test-optional-property .optionalCount=${state.count}></reduxular-element-test-optional-property>

Notice that the count value of reduxular-element-test-optional-property never updates.

It would be really nice to allow the top level component to hold all state, and pass state down to each component through props. This would make each child component in the tree more modular, without a dependency on a global Redux store. The big problem I see is making updates to the global store from within child components. There are a couple ways I can see to do it. One way is to raise an event when the global store needs to change. The top level component can register listeners for those events and then dispatch onto its store. The event handling will be asynchronous though, which might have drawbacks. It gets rid of the possibility of updating global state synchronously, and you have no way of awaiting the state change as far as I can tell.

Another way is to export the top level or pass it down through the props. But then that kind of defeats the while purpose of lossely-coupling the components and the global store. We've just added the dependency back.

If we can figure out how to await the global store change, that might work.