docs: document native Node.js ESM pitfalls

README.md

@@ -365,6 +365,27 @@ you find one, please).
 
 ## Upgrading From uuid\@7
 
+### Only Named Exports Supported When Using with Node.js ESM
+
+uuid\@7 did not come with native ECMAScript Module (ESM) support for Node.js.
+Importing it in a Node.js ES Module consequently imported the CommonJS source
+with a default export. This is no longer supported as this module now only
+provides named exports.
+
+Instead of doing:
+
+```javascript
+import uuid from 'uuid';
+uuid.v4();
+```
+
+you will now have to use the named exports:
+
+```javascript
+import { v4 as uuidv4 } from 'uuid';
+uuidv4();
+```
+
 ### Deep Requires No Longer Supported
 
 Deep requires, [which have been deprecated in uuid\@7](#deep-requires-now-deprecated) are now no

README_js.md

@@ -355,6 +355,27 @@ you find one, please).
 
 ## Upgrading From uuid\@7
 
+### Only Named Exports Supported When Using with Node.js ESM
+
+uuid\@7 did not come with native ECMAScript Module (ESM) support for Node.js.
+Importing it in a Node.js ES Module consequently imported the CommonJS source
+with a default export. This is no longer supported as this module now only
+provides named exports.
+
+Instead of doing:
+
+```javascript
+import uuid from 'uuid';
+uuid.v4();
+```
+
+you will now have to use the named exports:
+
+```javascript
+import { v4 as uuidv4 } from 'uuid';
+uuidv4();
+```
+
 ### Deep Requires No Longer Supported
 
 Deep requires, [which have been deprecated in uuid\@7](#deep-requires-now-deprecated) are now no