Bump file-loader dependency to latest (6.1.0)

[taylorreece]

Description

I'm having issues with a yarn workspaces environment that hosts both a gatsby-based site, and a https://github.com/facebook/docusaurus site. Gatsby and Docusaurus install different versions of a dependency, file-loader. Gatsby installs 1.1.11 from 3 years ago, and Docusaurus installs 6.0.0.

For some yarn-workspaces related reason that I don't fully understand, Docusaurus then winds up importing the older dependency that Gatsby specifies (facebook/docusaurus#3515) rather than the one that it specifies. This results in my Docusaurus site not being able to build, but if I remove the Gatsby project, the Docusaurus site builds fine.

I was curious if we could please bump the Gatsby dependency on file-loader? This PR does just that, and yarn test tests all pass after the version bump. Presumably this wouldn't cause regressions, then.

I fully recognize this isn't a Gatsby-specific issue... it's probably a webpack issue from what I can tell, but I'm new enough to node that I don't have a solid grasp on yarn workspaces and dependency resolution.

Anyways, thanks for your consideration!

Documentation

Related Issues

[ascorbic]

Hi. Thanks for this PR. We need to be a bit cautious here, as we've not updated this loader in several years, and this bumps it by five major versions. There are several breaking changes listed, and they might not be caught by our automated test. We need to investigate how we can appropriately test it.

[taylorreece]

Closing this out for now, as I realized that it won't actually fix my issue and those 5 major version bumps are probably more than a dummy like me can handle. Thanks for the great package - Gatsby rocks!