fix(gatsby-transformer-sharp) remove default export

[skovhus]

Description

This PR fixes a recent regression introduced in #20782, where a mix of import and require caused file extension warnings (e.g. You can't use childImageSharp together with x.png — use publicURL instead. The childImageSharp portion of the query in this file).

Related Issues

Fixed #21776

Next steps

I would love to introduce more safety nets in the code to avoid this problem in the future. Any plans to embrace TypeScript? Or limit the mix of import, default export, export, module.exports and require (this could be done using eslint)?

[LekoArts]

Hi, thanks for the PR! Seems like I goofed up there, sorry for that. We'll most likely switch our codebase to TS over time so in the future this (confusing) mix should be solved. Anyways, will publish quickly 👍

[gatsbot]

Holy buckets, @skovhus — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. We’ve got Gatsby t-shirts, stickers, hats, scrunchies, and much more. (You can also unlock even more free swag with 5 contributions — wink wink nudge nudge.) See gatsby.dev/swag for details.
2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. Accept the invite by visiting https://github.com/orgs/gatsbyjs/invitation. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!

[LekoArts]

Fixed in gatsby-transformer-sharp@2.3.16