Saransh Kataria

Born in Delhi, India, Saransh Kataria is the brain behind Wisdom Geek. Currently, Saransh is a software developer at a reputed firm in Austin, and he likes playing with new technologies to explore different possibilities. He holds an engineering degree in Computer Science. He also shares his passion for sharing knowledge as the community lead at Facebook Developer Circle Delhi, NCR which is a developer community in Delhi, India.
6 Ways to Detect and Prevent Fraud in Your Company

6 Ways to Detect and Prevent Fraud in Your Company

  • October 26, 2023

In the modern business landscape, fraud is a growing concern that no company can afford to overlook. A startling revelation from PwC’s Global Economic Crime and Fraud Survey from 2022 highlights this menace. Over half, precisely 51%, of the organizations surveyed reported experiencing fraud within the past two years. This...

Partial Matching in Jest

Partial Matching in Jest

  • October 25, 2023

Jest has the ability to check for partial matches on arrays and objects. Let us see how to do partial matching in Jest. expect has powerful matcher methods for partial matching, and they can also be combined with the tohavebeencalledwith method. Matching objects partially using expect.objectContaining When trying only to...

Fixing “error: cannot find module semver” error in Node.js

Fixing “error: cannot find module semver” error in Node.js

  • October 19, 2023

When installing a package using npm, you might encounter the “error: cannot find module semver” error. The error is caused because of a corrupted package-lock.json or yarn.lock. The most common reason for this is a change in the node version. Fixing “error: cannot find module semver” The fix is a...

Fix “Error:0308010C:digital envelope routines::unsupportedFixing” in Node.js

Fix “Error:0308010C:digital envelope routines::unsupportedFixing” in Node.js

  • October 17, 2023

Node 17 introduced OpenSSL v3.0, which brought in some breaking changes, and the “Error: error:0308010C:digital envelope routines::unsupported” is a result of one such change. It can be solved by passing in a “–openssl-legacy-provider” flag when running the application. Setting the NODE_OPTIONS environment variable We can set the environment variable that...