Repository navigation
Bug: Same named file resolve in different order than specified in extensions #438
Description
Activity
This would be a good regression fixture because the expected behavior is very concrete: with
extensionsordered as['.tsx', '.ts', '.json'], resolvingfooshould choosefoo.tsxbeforefoo.json. If the plugin currently delegates to a resolver that uses its own default extension order, the fix likely needs to ensure the configured extension list is passed through unchanged and tested with same-basename files in one directory.
Given 2 files
the statement:
loads the
.jsonfile and not the.tsx.The order of the extensions mentioned in the config (which lists json as last) does not seem to be relevant.