-
What version of the module is the issue happening on? Does the issue happen on latest version?
0.27.0
-
What platform and Node.js version? (For example Node.js 6.11.2 on Mac OS X)
10.17 mac OS
-
Sample source code or steps to reproduce
const handle = await lounge.connect({
connectionString: 'couchbase://127.0.0.1?detailed_errcodes=1',
bucket: REDACTED,
username: REDACTED,
password: REDACTED
})
(Write description of your issue here, stack traces from errors and code that reproduces the issue are helpful)
The above worked under Couchbase Node SDK version 2.4.6 (which meets Lounge's peer dependency) however the same results in "cannot read property username of null" under the 3.0.0 SDK version. If instead I try to connect to Couchbase as per the 3.0 documentation and then pass the bucket to Lounge via the bucket property of the connection options object I get an unhandled promise rejection error which seems odd since everything is using async/await inside of try/catch. My guess is that Couchbase Node SDK 3.0.0 now uses promises whereas the prior version did not and Lounge is assuming that it does not. The new presence of promises is possibly resulting in a double/nested promise situation where one is unresolved? Anyway, none of this is Lounge's fault -- of course -- I'm just curious if there are plans to support the 3.0.0 SDK.
Cheers -- and thank you.
What version of the module is the issue happening on? Does the issue happen on latest version?
0.27.0
What platform and Node.js version? (For example Node.js 6.11.2 on Mac OS X)
10.17 mac OS
Sample source code or steps to reproduce
(Write description of your issue here, stack traces from errors and code that reproduces the issue are helpful)
The above worked under Couchbase Node SDK version 2.4.6 (which meets Lounge's peer dependency) however the same results in "cannot read property username of null" under the 3.0.0 SDK version. If instead I try to connect to Couchbase as per the 3.0 documentation and then pass the bucket to Lounge via the bucket property of the connection options object I get an unhandled promise rejection error which seems odd since everything is using async/await inside of try/catch. My guess is that Couchbase Node SDK 3.0.0 now uses promises whereas the prior version did not and Lounge is assuming that it does not. The new presence of promises is possibly resulting in a double/nested promise situation where one is unresolved? Anyway, none of this is Lounge's fault -- of course -- I'm just curious if there are plans to support the 3.0.0 SDK.
Cheers -- and thank you.