create-react-app won't build when depending on obj-str

This is a weird one, and I bet this isn’t the right place for it. Running yarn build in my create-react-app project, it fails with:

$ react-scripts build
Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

        ./node_modules/obj-str/dist/obj-str.es.js:2 

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

error Command failed with exit code 1.

Following the link, it recommends filing an issue, even though I don’t see why this isn’t working.

My dependencies are:

"axios": "^0.16.2",
"date-fns": "^1.28.5",
"immutability-helper": "^2.4.0",
"lodash": "^4.17.4",
"normalize.css": "^7.0.0",
"obj-str": "^1.0.0",
"react": "^16.0.0",
"react-dom": "^16.0.0",
"react-redux": "^5.0.6",
"react-scripts": "1.0.14",
"redux": "^3.7.2",
"redux-devtools-extension": "^2.13.2",
"redux-thunk": "^2.2.0",
"reselect": "^3.0.1"

[lukeed]

Hey there,

Unfortunately, that’s because of this issue.

This module exposes a module entry in the package.json, which webpack will read by default. However, CRA doesn’t respond to this behavior, so the export default function()... statement is making it into your build, which then makes Uglify throw, then prints the message you received.

Closing since this is a heavily discussed CRA issue, but you could manually delete the module field on the node_module/obj-str/package.json file and you should be fine. Annoying, but it works.

FWIW: CRA should be adding a include function that only includes/compiles node_modules if they have a "module" entry. This is what we did in preact-cli for a while.

Hope that helps!

[lukeed]

@mrchief It should now be fixed 👍 I’m not sure how, but I forgot to publish v1.0.1 after producing fully transformed ES5 code (as seen in dist).

Long overdue now, apologies