gatsby-plugin-mdx doesn't find local plugins?

Is this expected? Known issue?

{
  resolve: `gatsby-plugin-mdx`,
  options: {
    gatsbyRemarkPlugins: [
      `my-local-plugin`, // doesn't work
      {
        resolve: require.resolve('path-to-my-local-plugin') // works
      }
    ]
  }
}

[pieh]

There are lots of interconnected issues here. Especially if the gatsby-plugin-mdx is declared in theme and not in top-level gatsby-config:

• https://github.com/gatsbyjs/gatsby/issues/21589
• https://github.com/gatsbyjs/gatsby/issues/21592

Note that the issues mostly talk about subplugins being npm packages, but it’s actually the same problem for local plugins

Exporting resolvePlugin alone wouldn’t be enough - there would also need to be some metadata of location of gatsby-config that declare given plugin to be able to resolve correctly (to use as rootDir param of `resolvePlugin).

On top of that, check this comment https://github.com/gatsbyjs/gatsby/pull/8379#issuecomment-585223189 about work on “selective cache invalidation” - for this to work Gatsby core will need to know about relationships between plugins/subplugins to properly clear caches and exporting resolvePlugin will “hide” this information from core, meaning that “selective cache invalidation” won’t have enough information to work properly.

[pieh]

I’ll close this issue, because the problem is already captured in https://github.com/gatsbyjs/gatsby/issues/21592 and there’s no point in having duplicates.

The resolvePlugin option is also already mention there (as well as some limitation of this approach)