Attempted to import the module "@react-native-ama/internal" which is listed in the "exports" of "@react-native-ama/internal"

Open
#319 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
react-native, typescript
Domain
mobile

Research direction

Start by reviewing commit 6c7ed2b48b9311547032876042f477c625c88997 and the package exports for @react-native-ama/core and @react-native-ama/react-native, then reproduce with React Native 0.79.2. Done means the iOS build no longer emits the unresolved @react-native-ama/internal export warnings.

Written by the indexing model from the issue text.

Description

bug
Is there an existing issue for this?
  • I have searched the existing issues
Code of Conduct
  • I agree to follow this project's Code of Conduct
Bug report

Full console warning:

Attempted to import the module "node_modules/@react-native-ama/internal" which is listed in the "exports" of "node_modules/@react-native-ama/internal", however no match was resolved for this request (platform = ios). Falling back to file-based resolution. Consider updating the call site or asking the package maintainer(s) to expose this API.

It might have been fixed in this commit, but I can't see the forms package installed in my node_modules to patch this change (I'm using RN only).

Repro steps:

  1. Install 1.2.0
  2. Use RN 0.79.2
  3. Build your app
  4. Notice in the console logs there are tons of Attempted to import the module.. warnings

Relevant package versions:

    "@react-native-ama/core": "^1.2.0",
    "@react-native-ama/react-native": "^1.2.0",
    "react-native": "0.79.2",
Dominant language
TypeScript
Stars
295
Forks
22
Avg merge
20m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FormidableLabs/react-native-ama

All issues in FormidableLabs/react-native-ama

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.