fix: edge function path parsing on windows #76
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We use some Node.js path parsing functions like
fileURLToPath()
,join()
, andrelative()
when extracting edge function files from eszip archives and normalizing paths for the LLM. Our edge function's paths (likeentrypoint_path
andimport_map_path
) are always in posix format, but the above functions will change behaviour based on the current running OS. This means that if you run the MCP server on Windows, it will fail to parse the above paths correctly.This PR fixes this to opt out of Windows path parsing and explicitly use posix paths.
Fixes #66