[docs] Further describe where gatsby-* files should belong in a gatsby plugin

[lannonbr]

Description

When @robert197 was creating a Gatsby plugin, he got caught up on where to place the gatsby-node.js file and it wasn't working for him. I helped debug his issue and it was that he didn't compile the code with babel from the src/ directory up to the root directory of his plugin.

The only place I found this noted to do this is in the last paragraph here: https://www.gatsbyjs.org/docs/creating-a-local-plugin/

It would be good to further document what files should belong in a plugin structure as well as expand upon transpiling the code with babel as many Gatsby plugins are done.

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 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. You can also add the label "not stale" to keep this issue open!

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/contributefor more information about opening PRs, triaging issues, and contributing!

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

[marcysutton]

This file exists now (the information was already there, just buried in another doc): https://www.gatsbyjs.org/docs/files-gatsby-looks-for-in-a-plugin/

The main action item I see here is to document transpiling of plugin code–but there are two things to note with that:

1. the transpilation plugin doesn't talk about how to operate on source code, only packages
2. Gatsby should probably just do that for you. @gatsbyjs/core any input on timing for when Gatsby will handle transpilation of packages automatically?

[sidharthachatterjee]

We do transpile all code in plugin packages since #15284

@robert197 Could you link to a reproduction because this sounds like a potential bug

[marcysutton]

This was opened before the transpilation of packages by default, so it might be a non-issue now!

[marcysutton]

I'm to close this issue as I believe it's resolved, but feel free to open if needed. Thank you!