Conversation
|
this deprecation warning annoys me a lot also ++++++++++ |
|
This deprecation is done only in Node.js 25 and above, I think. |
v22.12.0 deprecation gone after fix |
|
Thanks @denizyts. We will check this internally and make the change in the next release, if required (with due credits given to you :) ) |
|
@denizyts The strange thing is, I am not seeing this warning and I am also using Node.js 22. Can you give me an example, where you are seeing this warning? Are you using node-oracledb as part of any framework? |
|
Yes util.types.isDate should be ok but not util.isDate. Can you confirm if warning is from same file, |
|
I think the warning is coming from node-oracledb 5.5 |
|
Try polyfl: util.isDate ??= util.types.isDate; |
|
@denizyts @barisaydinayy What is the node-oracledb version that you are using? |
This deprecation related to oracledb version missmatch on local somehow, my version is 6.10.0 but the connection.js file still same with release 6.3.0 (probably caused by some conflicts with respect to local changes.) after 6.5.0 "util.types.isDate(value)" is used. So deprecation is gone. But still using "instanceof" is better approach i think. Thanks to @sharadraju and @sudarshan12s for responding <3 |
|
Thanks @denizyts. My guess is that your But we will discuss internally and see if we want to go ahead with |
(node:93573) [DEP0047] DeprecationWarning: The
util.isDateAPI is deprecated.This deprecation message annoys me a lot. I hope in the future versions it will be fixed or my pull request will be merged.