Skip to content
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

Bug: Object.hasOwn not supported in Node.js < 16.9.0 #160

Closed
morganwynne opened this issue Aug 15, 2023 · 2 comments
Closed

Bug: Object.hasOwn not supported in Node.js < 16.9.0 #160

morganwynne opened this issue Aug 15, 2023 · 2 comments
Assignees
Labels

Comments

@morganwynne
Copy link

DynamicsWebApi version
v2.0.0

Describe the bug
The retrieve method, and possibly other methods, utilizes Object.hasOwn, which is only supported by Node.js v16.9.0 and later. Unfortunately, when attempting to use the retrieve method on Node.js v15.14.0, it leads to compatibility issues and unexpected errors.

Actual result

TypeError: Object.hasOwn is not a function
at _clearRequestData (C:\\Lumen\\TruSales\\node_modules\\dynamics-web-api\\dist\\cjs\\dynamics-web-api.js:1440:14)
at _runRequest (C:\\Lumen\\TruSales\\node_modules\\dynamics-web-api\\dist\\cjs\\dynamics-web-api.js:1452:5)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:94:5)

Your Setup (please complete the following information):

  • Node or Browser: Node v15.14.0
  • Dynamics 365 Online or On-Premise: Online

Additional context
Thank you for your assistance in addressing this matter. Could you kindly provide information on the minimum version of Node.js that this package aims to support?

@AleksandrRogov
Copy link
Owner

hi @morganwynne , thank you for reporting this. I will release a patch as soon as possible. The minimum supported version for Node should be 15.0.

@AleksandrRogov
Copy link
Owner

Should be fixed in v2.0.1. Please let me know if you get any other issues related to v15.
I would recommend updating to v16 though, because v15 is out of maintenance and not being supported by the core Node.js team anymore.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants