-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(gatsby): fix api function compilation on Windows #38489
Conversation
import type { LoaderDefinition } from "webpack" | ||
|
||
const APIFunctionLoader: LoaderDefinition = async function () { | ||
const params = new URLSearchParams(this.resourceQuery) | ||
const matchPath = params.get(`matchPath`) | ||
|
||
const modulePath = this.resourcePath | ||
const modulePath = slash(this.resourcePath) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This just converts windows style file paths to unix one (so pretty much just \
-> /
), as windows style paths routinely has troubles with \
escaping and unix style paths don't even have to deal with escaping problem
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
(cherry picked from commit 26feae4)
(cherry picked from commit 26feae4) Co-authored-by: Michal Piechowiak <[email protected]>
Description
Changes done to API functions compilation recently (part of adapters work) caused a regression where functions fail to compile correctly on Windows (due to path seperator / escape interaction). This converts windows style path to unix style path in a place where it cause a problem (better/safer to normalize to unix ones than trying to ensure appropiate escaping
\
escaping is applied)Related Issues
Fixes #38481