margelo / margelo/react-native-fast-tflite

Unable to resolve module ../spec/NativeRNTflite

Open
#151 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.2k
Forks
92
Avg merge
13h 9m
Merged PRs (30d)
2

Description

Hi there, i've just installed the last version (1.6.1) and when triying to run my project (expo) for web. Im getting this error:

Image

I noticed that the file is on another folder:
instead of 'react-native-fast-tflite/lib/spec' (where current code is searching)

is on: 'react-native-fast-tflite/spec'

if i fix the path, changing
export { default as TensorflowModule } from '../spec/NativeRNTflite';
to
export { default as TensorflowModule } from '../../spec/NativeRNTflite';

Im able to compile it at least for web, but another error shows up:

Metro error: Cannot read properties of undefined (reading 'getEnforcing')

  TypeError: Cannot read properties of undefined (reading 'getEnforcing')

I belive thats because of this line:
export default TurboModuleRegistry.getEnforcing('Tflite')

At: 'react-native-fast-tflite/spec/NativeRNTflite.ts'

i've looked for others issues but none of them mention this one.

My setup:
"expo": "53.0.22",
"react": "19.0.0",
"react-native": "0.79.5",
"react-native-fast-tflite": "^1.6.1",
"react-native-vision-camera": "^4.7.2",
"react-native-worklets-core": "^1.6.2",

Thanks in advance!

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.

Research direction

Start with the package export that references ../spec/NativeRNTflite and the spec/NativeRNTflite.ts entry point, then reproduce the Expo web build using the listed React Native and Expo versions. Trace both the module-resolution failure and the TurboModuleRegistry.getEnforcing error; done means the intended web behavior is defined and the reported build errors are resolved or clearly documented as unsupported.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native, typescript
Domain
frontend, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.