You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When passing a path to wws (like wws ./examples), it should load the files starting from that route and assign the HTTP endpoint from it too. Currently, this is not the case and running wws ./examples when ./examples/handler.js exists will assign the /examples/handler route instead of the desired /handler.
In addition to that, in #3 @assambar described an issue when the folder does not include the trailing /. The trailing slash should be optional, so we need to fix that issue too.
The text was updated successfully, but these errors were encountered:
From #3 and #29
When passing a path to
wws
(likewws ./examples
), it should load the files starting from that route and assign the HTTP endpoint from it too. Currently, this is not the case and runningwws ./examples
when./examples/handler.js
exists will assign the/examples/handler
route instead of the desired/handler
.The issue is located at:
wasm-workers-server/src/router.rs
Line 71 in 4837e1b
Here we are removing
base_path
fromapi_path
, but in this case the string doesn't match properly:In addition to that, in #3 @assambar described an issue when the folder does not include the trailing
/
. The trailing slash should be optional, so we need to fix that issue too.The text was updated successfully, but these errors were encountered: