Any good reason for the project to still need "bluebird" as deps?
The long answer is it's absolutely everywhere in our codebases, with some code relying on catch-predicates, meaning we have to pull it out in exactly the right order else things will break in weird ways... and we haven't gotten around to tackling that yet.
Would love to get some help to get it out though - I raised an issue here: https://github.com/TryGhost/Ghost/issues/14882
Is this genuine ? So If I created a small PR refactoring out a bluebird style promise to native node it would be merged ?
do you have a plan to modernise these parts?