0.20.11 no longer exposes Bluebird interfaces
See original GitHub issueEnvironment
Knex version: 0.2.11 Database + version: PostgreSQL 10 OS: linux
Bug
The newly released knex version (0.20.11) breaks my application.
TypeError: this.db.select(...).from(...).limit(...).whereRaw(...).orderBy(...).map is not a function
It works just fine by rolling back to knex version 0.20.10.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:29 (7 by maintainers)
Top Results From Across the Web
@types/knex | Yarn - Package Manager
Fixes types for Seeder#run #3438. Test / internal changes: Execute CI on Node.js 13; Bluebird: remove usage of return , reflect , fromCallback...
Read more >knex - UNPKG
- Aggregate methods are no longer aliased as "aggregate", but may now be aliased and have more than one aggregate in a query...
Read more >Synthesis of Knowledge on the Effects of Fire and Fire ...
there is no such quantitative synthesis of the fire and fire-surrogate literature for ... bluebird density more than doubled in burn-only and thin...
Read more >20.04 - Ubuntu Packages
... files within Debian packages (command-line interface) apt-forktracer (0.7) [universe] utility for tracking non-official package versions apt-listchanges ...
Read more >s390 rawhide report: 20141025 changes - Fedora Mailing-Lists
No dependencies New package: perl-LV-0.006-2.fc22 Perl module to make ... Update to latest upstream release - Drop no longer needed patch, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
…This happens because you removed “Bluebird” dependency and returns a pure promise instead. This should have been a major change probably.
Yes that will work @briandamaged, but changing my code anyways it makes more sense to just adopt async/await style anyways.
But as @skreis points out your documentation kind of documents a bluebird like API.
Have you considered adopting a more “semver” like versioning? The current change is kind of dangerous as most people will use the
"knex": "^0.20.0"
syntax in their package.json and documented usages of the knex library breaks with the 0.20.11 release. Most npm user get it automatically because one expect patch releases to not change APIs.Any reason you are not ready to move towards a “1.0.0” release?
Anyways thanks for all the great work with knex, it has severed me well for many years!