Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

fix(gatsby): use file:// protocol when importing gatsby-config/node (#37257) #37260

Merged
merged 1 commit into from
Dec 14, 2022
Merged

fix(gatsby): use file:// protocol when importing gatsby-config/node (#37257) #37260

merged 1 commit into from
Dec 14, 2022

Conversation

gatsbybot
Copy link
Collaborator

Backporting #37257 to the 5.3 release branch

(cherry picked from commit e0ea47c)

@pieh @marvinjude
fix(gatsby): use file:// protocol when importing gatsby-config/node (#…
0f1a5d7 
…37257)

* fix(gatsby): use file:// protocol when importing gatsby-config/node

* Revert "fix(gatsby): use file:// protocol when importing gatsby-config/node"

This reverts commit 74d4090.

* different solution?

* only file://ify when importing

* update mock

(cherry picked from commit e0ea47c)
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Dec 14, 2022
@LekoArts LekoArts removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Dec 14, 2022
@marvinjude marvinjude merged commit a283319 into release/5.3 Dec 14, 2022
@marvinjude marvinjude deleted the backport-5.3-37257 branch December 14, 2022 11:50
# for free to join this conversation on GitHub. Already have an account? # to comment
Reviewers

@pieh pieh pieh approved these changes

Assignees
No one assigned
Labels
type: cherry
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@gatsbybot @pieh @LekoArts @marvinjude