Zero-config plugins, based upon the Next.js RFC

[kripod]

Summary

As an RFC about zero-config plugins has been submitted to Next.js, I thought a similar approach could be leveraged by Gatsby v3.

Motivation

Currently, some plugins should be loaded before or after specific packages (e.g. gatsby-plugin-offline should be listed after gatsby-plugin manifest in gatsby-config.js).

Zero-config plugins could define their own specificity relative to other known plugins, avoiding issues caused by a wrong loading order. For instance, gatsby-plugin-offline could define the following amongst its metadata:

{
  loadAfter: [‘gatsby-plugin-manifest’],
  // ...
}

This new approach would improve the experience for beginners and seasoned developers alike, lowering the burden caused by configuration management.

[gatsbot[bot]]

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

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

[KyleAMathews]

This is a cool idea. Thanks for bringing it to our attention!