4 ms·
Any good reason for the project to still need "bluebird" as deps?
by fbn79 4y ago
Any good reason for the project to still need "bluebird" as deps?
- erisds 4y agoGood question, the short answer is no :) 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 https://github.com/TryGhost/Ghost/issues/14882
- ushakov 4y agoi have the same question about jQuery and lodash (underscore) use in Ghost do you have a plan to modernise these parts?
- Dave3of5 4y ago> Would love to get some help to get it out though Is this genuine ? So If I created a small PR refactoring out a bluebird style promise to native node it would be merged ?
- jtwebman 4y agoI still use Bluebird library for things like property based promises resolutions and the map is a quick way to run only so many promises at a time instead of all of them or in series.