isparta-loader | isparta instrumenter loader for webpack | Plugin library

It seems that your node-gyp requires java to be built correctly. The thing with Heroku's architecture is that it only provides you what you specify/need. Right now I don't think Heroku understands that it needs a JVM to run your application. So you should provide a buildpack. A build pack put very simply is a set of rules telling Heroku what to set-up, install and build. There is a buildpack for JVM called heroku/jvm. So, what you have to do is add this to your application through the dashboard or your CLI via heroku buildpacks:add heroku/jvm.

There is one more thing to do. Since your app requires javac at build time itself, we should pull up the build order for java/jvm . So in that case you should probably do heroku buildpacks:add --index 1 heroku/jvm. This puts the JVM buildpack at position 1 and pushes every other buildpack down the order.

Now when the app starts building, it first sets up the JVM (thus enabling javac for your instance) and then runs the NodeJS build. This build will now pick up the javac from the current instance and build accordingly.

Ref: Mulitple Buildpacks in Heroku

You need to use Babel with a correct preset to parse the JSX syntax of your component, which is not supported by NodeJS, event in the latest version, and it will probably won't be supported in the future.

One option is to install the React preset and include it in a .babelrc file:

Just ran into the same issue today as well.

looks like react-addons-test-utils was deprecated https://www.npmjs.com/package/react-addons-test-utils

You can probably get away with replacing that line in your package.json with