This PR fixes the TypeScript module resolution error when importingReactNativeManualDevicePlugin using the documented path for Expo users.

Problem

Users following the documentation for Expo compatibility were getting TypeScript errors when importing:

import{ReactNativeManualDevicePlugin}from'@microsoft/applicationinsights-react-native/dist-esm/manualIndex';

The error was:Cannot find module '@microsoft/applicationinsights-react-native/dist-esm/manualIndex'

Root Cause

Thepackage.json exports field was missing an entry for the/dist-esm/manualIndex path that is documented as the recommended approach for Android/iOS Expo users. While the package supported the./manual export path, it didn't support the direct./dist-esm/manualIndex path that Expo users need.

Solution

Added a new export entry inpackage.json for./dist-esm/manualIndex that points to the same TypeScript definitions and JavaScript module as the existing./manual export:

"./dist-esm/manualIndex": {"types":"./types/manualIndex.d.ts","import":"./dist-esm/manualIndex.js"}

Impact

• ✅ Expo users can now successfully import using the documented path
• ✅ Existing imports using./manual continue to work unchanged
• ✅ Both paths point to the same implementation, ensuring consistency
• ✅ TypeScript correctly resolves types for both import paths
• ✅ No breaking changes to existing functionality

Testing

Verified that both import paths now work correctly:

• @microsoft/applicationinsights-react-native/manual (existing)
• @microsoft/applicationinsights-react-native/dist-esm/manualIndex (newly supported)

Fixes#46.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn moreCopilot coding agent tips in the docs.