fix(gatsby-plugin-mdx): fix gatsby develop on windows #31396
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gatsbot
bot
added
the
status: triage needed
pieh
added
topic: MDX
and removed
status: triage needed
vladar
approved these changes
May 13, 2021
|
is this fix in the v3.5 release? It defintely breaks any gatsby site using MDX on windows. |
vladar
pushed a commit
that referenced
this pull request
May 19, 2021
(cherry picked from commit ae2e2de)
vladar
added a commit
that referenced
this pull request
May 19, 2021
|
Published in |
|
I still have this problem while using |
hasparus
added a commit
to system-ui/theme-ui
that referenced
this pull request
Jun 10, 2021
2.5.1 is still broken on Windows. See gatsbyjs/gatsby#31396
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Current code doesn't work as expected on windows as
requestPathresult in in values like/src\\pages\\test.mdxand apparently webpack looses backslashes along the way (?)In any case, good old
slashto use slashes instead fixes the issueRelated Issues
fixes #31392