Skip to content
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-plugin-mdx): enable hmr when importing mdx (#31288) #31370

Merged
merged 1 commit into from
May 11, 2021

Conversation

gatsbybot
Copy link
Collaborator

Backporting #31288 to the 3.5 release branch

(cherry picked from commit c8db78f)

* save MDXContent to different file

* tmp: skip mdx loader unit tests

* test(e2e-mdx): upgrade cypress, setup running dev

* test(e2e-mdx): add hmr test case

* only apply hmr workaround to develop stage

* don't save mdx component to fs, use webpack tricks with query params

* wait for hmr in mdx/develop

* drop passthrough fs location

* revert unneeded change

* more reverts

* revert devtool debugging change

* adjust unit tests

* add more e2e test - editing prop in markdown, editing component imported by mdx

(cherry picked from commit c8db78f)
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 11, 2021
@vladar vladar removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 11, 2021
@vladar vladar merged commit baa0804 into release/3.5 May 11, 2021
@vladar vladar deleted the backport-3.5-31288 branch May 11, 2021 16:56
This was referenced Mar 13, 2022
This was referenced Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants