gulp-rev-replace | Rewrite occurences of filenames | File Utils library

I restructured the browserify-task and removed the rename, since the filename parameter in the vinyl-source-stream was already doing the renaming, I didn't really need it:

This usually means that one of the other project dependencies in your project.json has a dependency of lodash and they have not patched their pacakge.json.

The error states which one it is: "browser-sync-spa" and the path to it:

In your devDependencies, try downgrading this:

The answer is no in grunt-usemin, but in one of the dependencies: grunt-filerev. This last module is the one used to create the file revisions of you css, js and other files.

After grunt-filerev is executed (executed as a subtask of grunt-usemin), it creates a summary (stored in within your grunt task, under grunt.filerev.summary). The summary contains the following information:

The problem with this was that i had bootstrap.js included while having angular-bootstrap used, also.

In dev mode this was working just fine but when built, some dependency conflict broke the app. Removing standalone bootstrap did the thing.

What build pack are you using on heroku? Is it possible that you have an old version of express in heroku's npm cache? Try heroku config:set NODE_MODULES_CACHE=false and push a change to force a rebuild.

Also note that sendFile is present twice in your code so have you tried to replace it with sendfile at both places.

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

config-chain is npm dependency, so chances are that your npm installation is broken.

Try to reinstall it, or use one of npm forks if npm itself isn't installable on your system for some reason

Refer reinstall npm

I've actually found the solution and it was not at all obvious. One of the problems with Gulp, I've learned, is that by breaking everything down into little proprietary pieces, it's hard to see the big picture. That means that I needed to do some deep diving to discover what was wrong.

What was wrong was occurring prior to the useref stage. It was occurring when the pipeline was doing a .pipe(replace(, '