Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Issues with platform-specific React Native files
See original GitHub issueHey!
I was running this on my React Native project, and I noticed that it wasn’t able to follow an import such as ./User and resolve it to ./User.ios.tsx and ./User.android.tsx.
I realise this is an edge-case and might be difficult to solve since IIRC these special extensions are handled by Metro. Just wanted to surface this in case anyone else has the same issue. Luckily I have very few platform-specific files so this tool is still super valuable.
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sorry, even though I had a working version, it took me a while to commit. Mostly because I didn’t really like the solution.
I believe I’ve now found a better way to support this, and the commit has been pushed. It’s way more generic, and adds support for build configs like react native, but also other projects that have multiple build targets.
I’ll release this soon. All that’s left is add some presets / auto detection so that you don’t need to setup complicated unimportedrc config files.
@smeijer Thank you so much for looking into this! This feature would be super useful for React Native. If you need any help I’m happy to lend a second pair of eyes!