Make gatsby-remark-source-name compatible with gatsby v3

[Boelensman1]

Gatsby v3 has some breaking changes, this makes it work again.

I also bumped the version number as this would probably be a breaking change for gatsby-remark-source-name itself.

[AnnieTaylorCHEN]

Yeah I did that for my local repo but Netlify won't build properly unless we update this. Look forward to the update soon!

[raravi]

It would be awesome if this could be merged soon! One of my gatsby projects depends on this package, and its currently blocked from upgrading to Gatsby v3 due to this!!

I realised that its just a single file! I implemented it directly in my gatsby-node.js file.. :)

[AnnieTaylorCHEN]

It would be awesome if this could be merged soon! One of my gatsby projects depends on this package, and its currently blocked from upgrading to Gatsby v3 due to this!!

I realised that its just a single file! I implemented it directly in my gatsby-node.js file.. :)

Yes you can do that locally. However for deployment you might need to fork the project, change that line in package.json and point it to your forked and changed repo for the moment before this library finally updates. You might need to run a build on that one so it will be pulled correctly. I had to do that otherwise Netlify will have deployment error.

[raravi]

Oops, my bad. I meant you wouldn't even need this package.

In the gatsby-node.js file for your project, you can add the below code in exports.onCreateNode function directly:

const fileNode = getNode(node.parent);
    createNodeField({
      node,
      name: 'sourceName',
      value: fileNode.sourceInstanceName,
    });

[AnnieTaylorCHEN]

Oops, my bad. I meant you wouldn't even need this package.

In the gatsby-node.js file for your project, you can add the below code in exports.onCreateNode function directly:

const fileNode = getNode(node.parent);
    createNodeField({
      node,
      name: 'sourceName',
      value: fileNode.sourceInstanceName,
    });

Jaha, this is even simpler!