connect-flash | Flash message middleware for Connect and Express | Runtime Evironment 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:

Delete package lock file and Try using this command to rebuild the container.

Will express-flash work with clustering?

It depends upon whether you're running clustering-compatible session middleware.

The express-flash module uses the connect-flash module which stores its flash message in req.session. So, for a future request (often a redirect) to be able to access the flash message, the user's session has to be preserved.

So, if you're using a session implementation that is compatible with clustering, then express-flash will also work with clustering. If you either don't have any session support configured or the session you're using is not clustering compatible (e.g. not based on some centralized store that all clustered processes can access), then express-flash will not work properly.

So, it depends upon whether you're running a clustering-compatible session or not.

FYI, this doesn't really have anything to do with res.locals as that's not where the flash data is stored (since that's a temporary object that exists only for the duration of one request). That's just the final place that the data is placed by the flash middleware when there's an incoming request and it's placed there so that templates can access it if they wish.

You shouldn't use

the path would be

connect-flash does not use a default export. Use import * as flash from 'connect-flash' instead

Daniel If you are using views directory as a root you don't need to mention in app.js but if you are using partials and other directories at that time you have to mention those directories in app.js with path.

Hiding the link on the front end is, like you noticed, pointless. You need to implement the permission logic on the server. I haven't used Passport in a while (Meteor nowadays takes care of that nicely), but something like this should work:

First off, check the heroku docs to see the deployment cycle. Basically, the build script is ran after installing the packages (this is typically for bundling the frontend code but sometimes also for compiling the server code like if you've used TypeScript). Since you don't have any build being done, you should take out that line in your package.json file. (Esentially, what you'd done here was start your server twice)

Also, Heroku has it's own process monitor so no need to use nodemon. Change the start script to node app.js. You could also add a dev script that uses nodemon for your local development, then you'd run it using npm run dev.

So in summary, change the scripts config in your package.json file to below:

In order to access the req.files object, you need to add a specific middleware named express-fileupload that allows this functionality.

Simply run npm i express-fileupload, and then add it to your app.js, like so: