Module imports like use src/seedfile currently resolve relative to the source file's parent directory. This breaks when the entry point lives inside src/ (e.g., aster-pkg/src/main.aster importing use src/seedfile looks for src/src/seedfile.aster).
The fix: when a Seedfile exists in a parent directory, use it as the project root for module resolution. The resolver would walk up from the source file until it finds a Seedfile, then resolve imports relative to that directory.
Without a Seedfile, fall back to the current behavior (resolve relative to the source file). This keeps single-file scripts and test programs working unchanged.
Module imports like
use src/seedfilecurrently resolve relative to the source file's parent directory. This breaks when the entry point lives insidesrc/(e.g.,aster-pkg/src/main.asterimportinguse src/seedfilelooks forsrc/src/seedfile.aster).The fix: when a Seedfile exists in a parent directory, use it as the project root for module resolution. The resolver would walk up from the source file until it finds a Seedfile, then resolve imports relative to that directory.
Without a Seedfile, fall back to the current behavior (resolve relative to the source file). This keeps single-file scripts and test programs working unchanged.