How to target specific packages with babel-remove-graphql-queries

[iDVB]

We are having a problem similar to this one I think.
We have an internal UI package lib that we're trying to bake in some gatsby GraphQL queries into, to be compiled and removed by the consuming gatsby projects. However, we're getting the error:

It appears like Gatsby is misconfigured. Gatsby related graphql calls are supposed to only be evaluated at compile time, and then compiled away. Unfortunately, something went wrong and the query was left in the compiled code. Unless your site has a complex or custom babel/Gatsby configuration this is likely a bug in Gatsby.

Is there a way to setup the consuming project's gatsby config to specifically target our repo with babel-remove-graphql-queries? From the issue above, it sounds like by default packages with gatsby-* prefex are targeted.

I've tried whitelisting our package with onCreateWebpackConfig but with no luck...

exports.onCreateWebpackConfig = ({ actions, loaders, stage, getConfig }) => {
  const config = getConfig()
  config.module.rules = [
    // Omit the default rule where test === '\.jsx?$'
    ...config.module.rules.filter(
      (rule) => String(rule.test) !== String(/\.jsx?$/)
    ),
    // Recreate it with custom exclude filter
    {
      // Called without any arguments, `loaders.js()` will return an
      // object like:
      // {
      //   options: undefined,
      //   loader: '/path/to/node_modules/gatsby/dist/utils/babel-loader.js',
      // }
      // Unless you're replacing Babel with a different transpiler, you probably
      // want this so that Gatsby will apply its required Babel
      // presets/plugins.  This will also merge in your configuration from
      // `babel.config.js`.
      ...loaders.js(),
      test: /\.jsx?$/,
      // Exclude all node_modules from transpilation, except for '@klickmarketing/react-components'
      exclude: (modulePath) =>
        /node_modules/.test(modulePath) &&
        !/node_modules\/(OUR_PACKAGE_NAME)/.test(modulePath),
    },
  ]

  actions.replaceWebpackConfig(config)

I'm still getting the same error though.