I see now just a simple string concatenation of `directory_p` and `specifier`:

https://github.com/jerryscript-project/jerryscript/blob/0d4969661810b9e618485c284c361e597144e9b9/jerry-core/api/jerry-module.c#L141-L161

Does this mean that scenarios like absolute paths cannot be handled? My proposal for this is to add a parameter to `jerry_port_path_normalize` that specifies `directory_size` (which is also an offset to `specifier`).
Proposal for module path handling
This is a GitHub Issue
repo:jerryscript
owner:jerryscript-project
Title : Proposal for module path handling
Issue date:

--- start body ---
I see now just a simple string concatenation of `directory_p` and `specifier`:

https://github.com/jerryscript-project/jerryscript/blob/0d4969661810b9e618485c284c361e597144e9b9/jerry-core/api/jerry-module.c#L141-L161

Does this mean that scenarios like absolute paths cannot be handled? My proposal for this is to add a parameter to `jerry_port_path_normalize` that specifies `directory_size` (which is also an offset to `specifier`).
--- end body ---
