Improve path management in wws

[Angelmmiguel]

The wws server relies on the local filesystem heavily. The way we are managing paths at this point may cause issues when running the server in Windows environments. In addition to that, the way we check for multiple extensions is quite complex and error prone.

The goal for this issue is to:

• Define available extensions in a constant (in the future we may mek this configurable)
• Limit the conversion of paths to String and &str to printing data
• Rely on Path and PathBuf for any path management requirement

[assambar]

If the handlers folder is a flat one and I don't specify it with a trailing / I get 404 on the handler.

Given

$> tree /apps
/apps
└── handler.js
0 directories, 1 file

If I do this

wws /apps

I get no response to curl localhost:8080/handler in the shell and see a 404 in the server logs

[2022-10-18T14:55:01Z INFO  actix_web::middleware::logger] 127.0.0.1 "GET /handler HTTP/1.1" 404 0 "-" "curl/7.68.0" 0.000067

However, if I add an / at the end of apps it all works.

wws /apps/

[Angelmmiguel]

@assambar thanks for the report! The issue will be fixed in #30 😄

[Angelmmiguel]

The main issue we have here is the limitations of the glob library. The library doesn't support patterns with multiple extensions like **/*.{js,wasm}. We can chain multiple paths (iterators), but if the extensions are not hardcoded, we will need to flatten all the paths while we're reading the files.

The wax library is more up-to-date and covers the different use cases. I will switch to use this one.