feat: Support Node 17

[slorber]

Motivation

Docusaurus should run on Node 17

Change filename hash algo

https://webpack.js.org/configuration/output/#outputhashfunction

Fixes #5778

Note: it's not too important to use md5 in the file-loader because it's deprecated and using an older version of loader-utils (does not allow using xxhash64).

Have you read the Contributing Guidelines on pull requests?

yes

Test Plan

CI

[github-actions]

Size Change: +7 B (0%)

Total Size: 847 kB

ℹ️ View Unchanged

Filename	Size	Change
website/.docusaurus/globalData.json	38 kB	0 B
website/build/assets/css/styles.********.css	94 kB	0 B
website/build/assets/js/main.********.js	425 kB	+7 B (0%)
website/build/blog/2017/12/14/introducing-docusaurus/index.html	68.2 kB	0 B
website/build/blog/index.html	39 kB	0 B
website/build/docs/index.html	46.1 kB	0 B
website/build/docs/installation/index.html	53.6 kB	0 B
website/build/index.html	31.6 kB	0 B
website/build/tests/docs/index.html	27.3 kB	0 B
website/build/tests/docs/standalone/index.html	23.8 kB	0 B

_{compressed-size-action}

[netlify]

✔️ [V2]

🔨 Explore the source changes: cfeb69d

🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/617c0e06cb45900007652c36

😎 Browse the preview: https://deploy-preview-5814--docusaurus-2.netlify.app

[slorber]

Hmmm this is more complex as Webpack uses some hashes in prod in multiple places.

And it seems they plan to backport a MD4 hash impl here to fix the problem: webpack/webpack#14584

so it's probably not useful to change the hash algo for now

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	85
🟢 Accessibility	98
🟢 Best practices	100
🟢 SEO	100
🟢 PWA	95

Lighthouse ran on https://deploy-preview-5814--docusaurus-2.netlify.app/

[slorber]

Thanks @alexander-akait seems to be working :)

[alexander-akait]

@slorber Anyway, can you explain why file-loader is still used, maybe I can help or we can improve some things

[slorber]

@alexander-akait it's probably a lack of time/priority, I didn't work on it since last time.

Also not sure how to do this migration without using a oneOf rule, which is likely a breaking change for our plugin ecosystem using a configureWebpack(config) lifecycle. Doing that seems likely to be annoying.

webpack/webpack#12900 (comment)

[alexander-akait]

hm, I see... yes need may have to experiment or enter a new option...