[gatsby-recipes] Remove duplicate Babel install

[aaronadamsCA]

The package remark-mdxjs is deprecated and no longer being published:

https://github.com/mdx-js/mdx/tree/main/packages/remark-mdxjs

According to its README its behaviour is now included in remark-mdx.

remark-mdxjs had an unranged outdated @babel/core dependency. The result is an entire second Babel install when installing Gatsby.

I think these lines should all be safely removable:

gatsby/packages/gatsby/package.json

Line 241 in df3f184

"remark-mdxjs": "^2.0.0-next.3"

gatsby/packages/gatsby-recipes/package.json

Line 53 in df3f184

"remark-mdxjs": "^2.0.0-next.4",

gatsby/packages/gatsby-recipes/package.json

Line 122 in df3f184

"remark-mdxjs": "^2.0.0-next.4"

gatsby/packages/gatsby-recipes/src/parser/index.js

Line 3 in 54d4721

import remarkMdxjs from "remark-mdxjs"

gatsby/packages/gatsby-recipes/src/parser/index.js

Line 54 in 54d4721

.use(remarkMdxjs)

There are probably other references to the package to clean up as well.

[vladar]

Thanks for the suggestion @aaronadamsCA Are you up to opening a PR with this change?

[jithenms]

I'd be able to find the references and remove and replace the dependency. Let me know if I could work on this if you both prefer. Thanks!

[jithenms]

Hi, I had some time tonight and went ahead and completed the issue. Hope it saves you time from doing it yourself.

Just submitted a PR for review. Thanks!

[LekoArts]

The opened PR is invalid now (as the fork was deleted) so we're still open to PRs!

[Harshita-Kanal]

I will take this up :)

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[github-actions]

Hey again!

It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to comment on this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜

[aaronadamsCA]

Retitled to clarify why this should be done. Seems the existing PR is dead, so @LekoArts I can try picking this up myself.

[LekoArts]

Cool!

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[aaronadamsCA]

Not stale.

I think #32377 should be fine despite the failing tests, since I'm pretty sure that's just intermittent failure (likely because Yarn v1 is broken/dead and rarely builds a valid dependency tree). But if anyone else sees anything to add, please comment!

[amitsin6h]

taking up on this issue

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[aaronadamsCA]

Happy to update the PR if someone can commit to review and merge before it goes stale again :)

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[github-actions]

Hey again!

It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to comment on this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜

[aaronadamsCA]

@LekoArts / @vladar , could you reopen?

Happy to redo the PR anytime, but last time it just sat there unreviewed until it was stale, so I'd like to know it'll get merged before I take the time again :)

[LekoArts]

Actually our goal is to remove gatsby-recipes completely so at quick glance this should solve it, too, right?

[aaronadamsCA]

Yes, absolutely. Thanks for confirming, then! Let me know if there's anything I could do to help with that initiative.