-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breaking change removing bluebird #266
Comments
My sincerest apologies, I'd forgotten that bluebird was part of the interface. In the mean time - which node version are you using? if >=6.x you should be able to change that line with: .then(([resA, resB]) => { /* ... */ } |
@AlexisNo - ok, I have an alternative solution that should offer most of what bluebird did at a fraction of the footprint. |
Personally, I like to use I think it is possible to exclude bluebird and allow the user to inject a Promise lib. Mongoose has this functionality. I implemented it for a small module too. This way you do not need to pull bluebird back in and users are free to use their favorite Promise implementation. Thanks for the fix. It is true that this ES6 syntax makes const Promise = require('bluebird');
return Promise.resolve(workbook.xlsx.readFile(file))
.then( /* ... */ )
.spread( /* ... */ ) It looks more like a hack, but I don't need to change every |
Once again - sorry for the break.
|
Awesome! Thank for the quick fix. |
Hi, thanks for the great work on this lib.
The removal of bluebird introduce a breaking change. I think the version number of the lib should have changed accordingly.
Indeed, the
spread
method disappeared.TypeError: [...].spread is not a function
I think the use of
spread
is very common for bluebird users. I my case, my build was broken by this minor version change.Ideally, we should have the possibility to inject bluebird in ExcelJS to continue to use it.
The text was updated successfully, but these errors were encountered: