Allow require to load file-type as ES Module

[Borewit]

Add module-sync in exports, allowing require-esm loading file-type with Node.js ≥ 22.

Discussion: #722 (comment)

Superseding:

• fix: Fix require(ESM) for Node v22 #722
• fix: Fix require(ESM) for Node v22 #723.

Related:

• Add CommonJS entry points #665
• Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in \node_modules\file-type\package.json #696
• file-type ERR_PACKAGE_PATH_NOT_EXPORTED typescript #671
• Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined #668
• ERR_PACKAGE_PATH_NOT_EXPORTED when file-type used in nest.js #661
• Unable to use plugin: Error [ERR_REQUIRE_ESM]: require() of ES Module #600

[imaksp]

good, waiting for this, require esm support will also land in Node 20 LTS soon.

[Borewit]

As pointed out here: #737 (comment)

At least 9 out of 10 of our users are still CommonJS users

Looking at the statistics of the last 7 days, 89.2% of the downloads are still CommonJS and just 10.8% are ESM versions. That tells me, despite ESM is around for many years, there is still a significant demand from CommonJS projects.

The actual number of CommonJS dependent projects / users is even higher, as CommonJS projects which are already importing file-type as an ESM module are counted as ESM downloaders.

With this PR we likely closing the gap for many, as there is clear bottleneck on the latest CommonJS version, which is still the most frequently downloaded version by far.

[Borewit]

@sindresorhus, in reply to #741 (comment)

We can use await import inside the function.

This is a misunderstanding Sindre. It is certainly also possible to use dynamic imports with "module-sync". The restriction is:

The format is expected to be ES modules that does not contain top-level await in its module graph

So this is not allowed:

// ESM Entry point file

// Top level await
export quoteOfTheDay = await fetch('https://www.forbes.com/forbesapi/thought/uri.json?enrich=true&query=1&relatedlimit=1');

But this is totally fine:

// ESM Entry point file

export async function detect(buffer {
  const {fileTypeFromBuffer} = await import('file-type'); // dynamic import
  return fileTypeFromBuffer(buffer );
} 

[sindresorhus]

This is a misunderstanding Sindre.

That is completely unrelated to this issue. There I'm talking about using await import to be able to import node:fs.

[Borewit]

Merged with #741, part of v20.3.0