Oxlint reports incorrect errors when it receives a relative path starting with ..

[ah-yu]

test_repo % npx oxlint@latest --import-plugin ../test_repo 
× Failed to open file "test_repo/foo/bar/index.js" with error "No such file or directory (os error 2)"
help: Failed to open file "test_repo/foo/bar/index.js" with error "No such file or directory (os error 2)"

The error reported by oxlint appears to be incorrect. In fact, the file test_repo/foo/bar/index.js exists. It seems to be an issue related to oxc_resolver.

// enhanced resolver
resolve.sync("../test_repo/foo/bar", "../main") // returns "../test_repo/foo/main.js"

// oxc_resolver
resolver.resolve("../test_repo/foo/bar", "../main").unwrap() // returns "test_repo/foo/main.js"

[IWANABETHATGUY]

https://github.com/oxc-project/oxc_resolver/blob/4585b370614fdfc8cd8c473e94c0aa35770f82ef/src/cache.rs#L192-L192, fs.canonicalize will strip the ../

[IWANABETHATGUY]

the implementation of oxc_resolver does not looks wrong, call site could canonicalize the path before resolving, here is a example https://github.com/oxc-project/oxc_resolver/blob/4585b370614fdfc8cd8c473e94c0aa35770f82ef/examples/resolver.rs#L10-L10.

[IWANABETHATGUY]

I can replicate the issue with a relative path, could you provide a reproduce repo?

[ah-yu]

could you provide a reproduce repo?

https://github.com/ah-yu/resolver-test

[IWANABETHATGUY]

  ⚠ eslint-plugin-unicorn(no-empty-file): Empty files are not allowed.
   ╭─[../test_repo/foo/bar/index.js:1:1]
   ╰────
  help: Delete this file or add some code to it.

  × Failed to open file "test_repo/foo/bar/index.js" with error "No such file or directory (os error 2)"
  help: Failed to open file "test_repo/foo/bar/index.js" with error "No such file or directory (os error 2)"

looks like we read the same file twice when enabling import-plugin ? @Boshen

[Boshen]

I decided to disallow supplying paths pointing to parent directories, the intention is not clear and it will introduce undefined behaviour.