tap is not a function
See original GitHub issueEnvironment
Knex version: 0.19.0
Example:
knex(tableName).select().tap().then(result => {
console.log('success')
});
Result:
TypeError: knex(...).select(...).tap is not a function
Expected result:
success
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Why this Tap function script is not working? - Stack Overflow
I want to put tap function in other content too but it is not working. when you click tap on the top, each...
Read more >The Wide Area Tap function of the Linkbuds does not work as ...
Try the following procedure to verify that the Wide Area Tap function is working. Restart the connected device.
Read more >.tap | bluebird
If the handler function passed to .finally returns a promise, the promise returned by .finally will not be settled until the promise returned...
Read more >Asserts - Node Tap
Verifies that the promise (or promise-returning function) resolves, and furthermore that the value of the promise matches the wanted pattern using t.match ....
Read more >Why you need the tap method - DEV Community
Interesting... but you need a warning that this is an anti-pattern: Array.prototype.tap = function() { // ... }; You should almost always avoid ......
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
@elhigu 0.19.0 was released, actually. I will fix docs ASAP and hopefully release 0.19.1 tonight.
@ivanovych666 It is, indeed, a breaking change, which is why it was included in 0.18.0 release, and communicated in migration guide (https://github.com/tgriesser/knex/blob/master/UPGRADING.md) ->
Knex returns native promises instead of bluebird ones now. You will need to update your code not to rely on bluebird-specific functionality;
. If you can’t currently migrate your codebase to work with native promises, you should use 0.17.xThere was high demand from community to replace bluebird promises with native ones, and given the current direction of broader Javascript ecosystem, it definitely makes sense.