load-grunt-tasks | Load multiple grunt tasks using globbing patterns | DevOps library

Node.js 4.4.4 is absolutely ancient.

It doesn't even show up on this page of releases, which says in part:

After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.

Version 4.4 is well beyond its maintenance window, and I strongly urge you to upgrade this project.

Having said that, there's a good chance you can get Heroku to run Node.js 10 to match your local version. Heroku only officially supports the current and active LTS releases, but it doesn't prevent you from using older releases:

Since Heroku is based on a standard Ubuntu Linux stack, you can run most Node versions (>= 0.10.0) on the platform. However, the testing and support focus of the buildpack will be oriented around active LTS and Stable releases.

Update the engines section in your package.json:

There is some information missing, like the project you forked off and the package.json dependencies.

Luckily, I found https://github.com/bpmn-io/bpmn-js-diffing and that's probably the project you forked. Lets note that this project is very old and so are its dependencies, which I had to fix for it to work, so the versioning alone might change my results from yours.

What I didn't find were minified contents. The file app/bpmn-viewer.js is the concatenation result. The multiple files are concat into this one, yes, but there's only the browserify header that is always minified within bpmn-viewer.js.

First off, you commented load-grunt-tasks and the "default" grunt task, so I'm not sure you really ran grunt of this Gruntfile.js. Commenting it out cannot work, because there are no calls to grunt.loadNpmTasks as far as I'm aware, grunt plugins are not loaded without any loading instruction.

Now to the documentation. You are right that the concatenation happens because of the files field. This is part of Grunts Task definition layout.

Browserify analyzes the given files and concats them into one. That's the abstract description, more of that in the browserify handbook.

Still keep in mind: The versions of your forked project are very old.

So here's what I could find out in short:

• No, the contents are not minified
• A browserify header (which are minified) and the source map contents are added to the final file

If you really have minified content, please provide the package.json dependencies and the real running Gruntfile.js.