OutgoingMessage._headers deprecated warning when using fileNode mapping in Gatsby Airtable plugin

Other Questions Airtable
1

I keep running into a deprecation warning during my Gatsby build process. This happens right after I add the fileNode mapping for photos in my plugin settings.

The error message I’m seeing is:

(node:12345) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
(Use node --trace-deprecation ... to show where the warning was created)

Here’s my current plugin configuration:

{
  resolve: `gatsby-source-airtable`,
  options: {
    apiKey: process.env.AIRTABLE_KEY,
    tables: [
      {
        baseId: process.env.BASE_ID,
        tableName: process.env.TABLE_NAME,
        mapping: { photo: `fileNode` },
      },
    ],
  },
}

I think this might be related to how the Airtable source plugin handles the filesystem integration. When I check older versions of gatsby-source-filesystem (anything below version 3.0.0), I don’t see this warning at all.

Has anyone else run into this issue? I’m not sure if this is coming from the Airtable plugin itself or if it’s a problem with how it interacts with the filesystem plugin.

2

i had the same problem! i rolled back to gatsby-source-filesystem 2.11.1 and it fixed the warning for now, but it feels like a stopgap solution. hope they release a patch soon!

3

This warning typically occurs when there is a mismatch between the versions of your Airtable plugin and the filesystem dependencies. The OutgoingMessage._headers deprecation warning indicates that Node.js has altered its internal APIs, and newer versions of gatsby-source-filesystem handle this change differently. From my experience, updating both gatsby-source-airtable and gatsby-source-filesystem to their latest compatible versions usually resolves the issue. Additionally, ensure that other plugins relying on gatsby-source-filesystem are also compatible. While your build process won’t fail due to this warning, the plugin’s reliance on deprecated Node.js APIs could lead to complications with future Node releases.