What was reported:
Issue auth0/node-auth0#952 (closed, 8 comments): ### Checklist - [X] I have looked into the [Readme](https://github.com/auth0/node-auth0#readme), [Examples](https://github.com/auth0/node-auth0/blob/master/EXAMPLES.md), and [FAQ](https://github.com/auth0/node-auth0/blob/master/FAQ.md) and have not found a suitable solution or answer. - [X] I have looked into the [API documentation](https://auth0.github.io/node-auth0/) and have not found a suitable solution or answer. - [X] I have searched the [issues](https://github.com/auth0/node-auth0/issues) and have not found a suitable solution or answer.
What works:
If the auth0 v4 package's TypeScript definitions confuse your IDE by exposing duplicate module-specific paths (like auth0/dist/cjs/management), do not import from those paths. Set `"moduleResolution": "node16"` in tsconfig.json so TypeScript respects the package's exports field; the old node10 resolution is what surfaces the duplicates, and the maintainers closed this as by-design for node10. Related: ApiResponse not being exposed was a real bug, fixed in PR #954.