yarn deploy fails to build a mirror-saga dependencies

[francisrod01]

Environment

1. node -v: 9,3,0
2. npm -v: 5.5.1
3. yarn --version (if you use Yarn): 1.5.1
4. yarn list react-scripts (if you haven’t ejected): 1.1.1

Then, specify:

1. Operating system: Linux Version 3.16.0-5-amd64, Debian 3.16.51-3+deb8u1 (2018-01-08)
2. Browser and version (if relevant): Google Chrome Version 65.0.3325.162 (Official Build) (64-bit)

Steps to Reproduce

1. I'm trying to build a project using yarn and react-app-env
2. Failed to minify the code from this file:
3. I try to use `@babel/preset-env to fix it
4. I write a .baberc file but didn't work.

Expected Behavior

Compile my mirror-saga dependencies correctly.

Actual Behavior

$ firebase use default && react-app-env --env-file=.env.prod build
Now using alias default (opevere-game)
Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file: 

 	./node_modules/mirror-saga/src/index.js:4:28 

Read more here: http://bit.ly/2tRViJ9

Done in 18.24s.

.babelrc file:

{
    "presets": [
        ["@babel/preset-env", {
            "targets": {
                "esmodules": true,
                "browsers": ["last 2 versions", "safari >= 7"]
            }
        }]
    ]
}

error output:

$ head -n 10 ./node_modules/mirror-saga/src/index.js 
import sagaMiddleware from './middleware'
import addEffect from './effects'

export default (options = {}) => {
  const middlewares = options.middlewares || []
  // overwrite defaults
  return Object.assign(options, {
    middlewares: middlewares.concat([sagaMiddleware]),
    addEffect,
  })

Yes, it compile as well without mirror-saga.

[ShMcK]

Sorry I haven't been very helpful or fast at responding to issues for this repo.

I haven't had much free time over the past few weeks to contribute to OS.

I no longer use this package, and currently use rematch instead of Mirror.

I think the simplest solution here is to mark this package as deprecated in the README. Feel free to fork it and take it over. Open source can be frustrating at times. My apologies.

[Timer]

Using react-scripts@2 should fix this error.