Lars Kappert

Closing due to inactivity.

Interesting. How could Knip know about such platform-specific conventions? Sounds like it's not a generic file name convention like `index.ts`, but rather any component file such as `Button.tsx` must have...

This is all specific to React Native, right? And *any* "base" source file could have one or more platform-specific "sibling" files? This isn't about calculating the dependency tree and then...

Yes, that's what I meant: walk the file tree and look for `something.[ios|android].js` etc and see if `something.js` is there as well. If not, that's an issue. That's basically all...

I meant something like this (generated by chatpgt): ``` #!/bin/bash find . -type f \( -name "*.android.js" -o -name "*.ios.js" \) | while read -r file; do base="${file%.*.*}" [[ !...

To re-iterate: - Knip only considers imported files, the rest is reported as being unused - The `*.[platform].ts{,x}` files can be ignored in Knip config - Knip will report unused...

So, I took a stab at it. Thanks a lot @lindboe and @neiker for the details. The implementation of [metro-resolver](https://github.com/facebook/metro/tree/main/packages/metro-resolver) was useful too. The challenge here is that it's not...

@alburdette619 Any chance you can share a repo or a reproduction? I can't see or debug anything without an actual codebase.

> Just following this, but to add: > > > The plugin is activated if @react-native/metro-config is in the list of dependencies. Is that enough? > > Expo apps (an...

> Fairly simple to reproduce the exports issue: > > [..] > > Knip reports that the default exports are unused. Not sure I understand this output. Not seeing any...