unexpected behavior at vvisp-utils/src/compiler.js:findImports

[cloudinertia]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:

Current behavior

findImports is dependency resolver while compile.
Current implementation use node-find-folder for find filepath of target contract.
But, node-find-folder's out often does not behave what we expect.

For example, assume we have follow directory tree

contracts/
MainContract.sol
lib/
Ownable.sol
external_folder/
Ownable.sol
And at MainContract,
import "./libs/Ownable.sol" -> here we might expect Ownable.sol would be at contracts/lib/Ownable.sol

But node-find-folder doesn't ensure that behavior, so that it has a chance to compile unexpected soruce file.

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

vvisp version: X.Y.Z


Environment:
- Node version:
- Operating system:

Others: