docs: add ESM example to profiles documentation (#2599)

Co-authored-by: Claude <[email protected]>
Co-authored-by: David Goss <[email protected]>

Author: 3 people

docs/profiles.md

@@ -14,7 +14,7 @@ The short tag is `-p`
 cucumber-js -p my_profile
 ```
 
-## Simple Example
+## Simple example
 
 Let's take the common case of having some things a bit different locally than on a continuous integration server. Here's the configuration we've been running locally:
 
@@ -67,6 +67,31 @@ Now, if we just run `cucumber-js` with no arguments, it will pick up our profile
 cucumber-js -p ci
 ```
 
+## ESM example
+
+When using ES modules, you should use a default export for your default profile and named exports for additional profiles:
+
+```javascript
+const common = {
+  requireModule: ['ts-node/register'],
+  require: ['support/**/*.ts'],
+  worldParameters: {
+    appUrl: process.env.MY_APP_URL || 'http://localhost:3000/'
+  }
+}
+
+export default {
+  ...common,
+  format: ['progress-bar', 'html:cucumber-report.html'],
+}
+
+export const ci = {
+  ...common,
+  format: ['html:cucumber-report.html'],
+  publish: true
+}
+```
+
 ## Defining profiles dynamically
 
 If you need to define your profiles dynamically (including asynchronously), you can use the `default` profile key/export to provide an async function that resolves to your profiles. This can be particularly useful in an ESM context where the profiles are static exports. Here's an example:

package.json

@@ -100,6 +100,7 @@
     "Krispin Schulz <[email protected]>",
     "Kushal Pisavadia",
     "Kyle Moore <[email protected]>",
+    "lackita (https://github.com/lackita)",
     "Leonardo <[email protected]>",
     "Long Nguyen (https://github.com/zcmgyu)",
     "lopesc <[email protected]>",