You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 29, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 29, 2026. It is now read-only.
/var/lib/openshift/XXXXXXXXXXXX/app-root/runtime/repo/node_modules/connect-mongo/src/index.js:3
const Promise = require('bluebird');
^^^^^
SyntaxError: Use of const in strict mode.
Mmm, this is because of the quite old Node version you & Openshift are using. For now I'd suggest re-installing the latest connect-mongo and importing connect-mongo/es5 instead of connect-mongo, or updating to Node 4.x.x+
Ideally openshift would have a more up to date version of Node, I run 4.x locally but alas community managed deployments are a ways behind. Thanks for the advice.
@Awk34 I suppose it would be, I will have to look into how that would work with the app deployment, as you know when using buildcontrol it decides the node module it deploys as. Prior to this change I quite literally didn't need to think at all about openshift deployments using angular-fullstack, just let my fingers do the walking and trust that it was configured to work. I could setup an account for a client, deploy to that account and point a dev domain in under an hour which was awesome. BTW angular-fullstack makes my life so much simpler thank you ; )
Activity
Awk34 commentedon May 3, 2016
Mmm, this is because of the quite old Node version you & Openshift are using. For now I'd suggest re-installing the latest connect-mongo and importing
connect-mongo/es5instead ofconnect-mongo, or updating to Node 4.x.x+unsalted commentedon May 3, 2016
Ideally openshift would have a more up to date version of Node, I run 4.x locally but alas community managed deployments are a ways behind. Thanks for the advice.
Awk34 commentedon May 3, 2016
@unsalted would adding something to the readme about updating the node version in Openshift help? I found this article: https://blog.openshift.com/any-version-of-nodejs-you-want-in-the-cloud-openshift-does-it-paas-style/
unsalted commentedon May 3, 2016
@Awk34 I suppose it would be, I will have to look into how that would work with the app deployment, as you know when using buildcontrol it decides the node module it deploys as. Prior to this change I quite literally didn't need to think at all about openshift deployments using angular-fullstack, just let my fingers do the walking and trust that it was configured to work. I could setup an account for a client, deploy to that account and point a dev domain in under an hour which was awesome. BTW angular-fullstack makes my life so much simpler thank you ; )
Awk34 commentedon May 6, 2016
@unsalted I think what I might do for now is include
connect-mongo/es5if an older Node version is detected.