Expected Behavior

I expect my app to build both in dev and in production.

Current Behavior

Build fails with both razzle start and razzle build.

Steps to Reproduce

1. install and import aws-amplify-react

Detailed Description

Here is the error trace:

PROJECT_DIR/node_modules/@aws-amplify/ui/dist/style.css:13
:root {
^

SyntaxError: Unexpected token :
    at Modul

Lot of packages depend on bs-react-native, such as this. We'll need to work with these package owners to migrate to the next release of reason-react-native.

Preliminary list from npm search:

• [ ]

When loading the website via Safari 12.0 (13606.2.11), the same icon for the 💬 bubble is requested repeatedly.

According to reason-react docs instance variables should be stored in state and be marked with ref instead of mutable to prepare for concurrent react.

I am unsure whether this makes any difference for a global state management solution like reductive, but would be nice to have a better insight into thi

It would be great to have a couple of example apps, similar to Redux and co. inside an examples folder in the repo.

Describe Container and Link props and behavior

Calls to dispatch currently results in deferred execution of the reducer and does not guarantee that messages are processed in the order they were dispatched. This can cause subtle bugs when the reducer has side-effects that depend on ordering.

I understand the motivation for this is to have potentially blocking calls in the reducer not block the UI thread. As I understand it, the deferred

We should write some documentation along the lines of what StackOverflow has written on the topic, and then present it in some form on the same page.

Next.js includes additional API for creating a custom top-level document. There are currently no bindings present for them.

• Document
• Head
• Main
• NextScript