react-redux-starter | Large scale project development boilerplate | State Container library

It seems there are some issues regarding the node:8-alpine image that you are using. See https://github.com/puppeteer/puppeteer/issues/379. I don't know if it's the same issue but I was able to run your tests using the node:8.15-slim as the base image of your base Dockerfile

You'll need to update your dev Dockerfile as well:

It is only a warning as it won't actually stop your code from running, It's just there to give you a heads up that there's something wrong with your dependencies.

Effectively, peer dependencies are a way for packages to specify, "to use me, you should also have x version of y package installed".

You should upgrade to the latest versions, see this link for more details on sass-loader dependencies

I think that if you don't want to use relative paths, you have to define additional moduleDirectories, like

Several issues I can point out:

• You seem to be declaring and spinning a pact mock server twice: in the src/pactSetup.ts file and also in TotalPayout.test.pact.ts which I'm not sure it's what you intended to do. You probably want to avoid declaring the provider in the TotalPayout test, and instead you already have the provider object on the global scope as part of the test framework setup files.

• In the code apiPayout.ts you are referring to the endpoint URL, but to which port is it sending the request? This API call should be ultimately caught by the pact mock provider that you are spinning up. If you call to a different port than what the mock provider is listening on you'll never hit it.

• A small nitpick: /frontoffice/api/get-total-payout is not a RESTful. You want to avoid including verbs such as "get" in your API and use the proper HTTP method for that (GET).

Totally guessing here, but it's possible that the error is coming from the fact that you're dispatching a Promise here:

If your React dev server origin is differs from Rails application server origin (even just by port number), Rails thinks that request is cross-origin.

When Rails receives such request it denies it unless CORS policy is set up.

The easiest way to do so is (probably) to use rack-cors gem:

1) Add

according to this link it's considered bad practice to import a libraries sources directly. You can avoid this problem by simply importing the compiled version. Just change import { db } from 'baqend/lib/baqend' to import { db } from 'baqend' in all your application sources (store.js and Messages.js in the starter) and it should work. Thank you for pointing this out.

I have been experiencing similar issues with Vagrant 1.8.7 and Virtualbox 5.1.10. I was able to fix the filesystem readonly problematic by reducing the number of cpu cores to 1:

By default redux expects actions to be plain objects. If you want to write some asynchronous code and return a promise you need to use some kind of middleware, redux-thunk would be a great option.

The README page of redux-thunk is actually quite documented, and there is a full example there. Basically you need to apply the redux-thunk middleware to your store like this: