@gnuechtel/nx-cucumber 2.1.0 → 2.1.1

package/README.md

@@ -18,6 +18,8 @@ Plugin to use Cucumber within Nx workspaces
   - [Inferred tasks](#inferred-tasks)
   - [Plugin registration](#plugin-registration)
   - [Cucumber configuration](#cucumber-configuration)
+    - [Default configuration](#default-configuration)
+    - [Config file formats](#config-file-formats)
   - [World parameters](#world-parameters)
   - [Enable videos](#enable-videos)
   - [Change screenshot options](#change-screenshot-options)
@@ -67,7 +69,7 @@ Version 2.x is a deliberate breaking release that simplifies the plugin architec
 - **Faster execution.** Removing the executor bootstrap, in-process Cucumber API, plugin-managed dev server lifecycle, and report post-processing from the execution path results in faster test runs.
 - **Reporting is formatter-first.** Generated projects now rely on Cucumber-native formatters (`html`, `json`, `message`, `junit`) plus a dedicated run-metadata formatter artifact. No HTML mutation layer is used.
 - **Legacy HTML post-processing removed.** The previously exported `createBeautifulHtmlReport` helper and `cucumber-html-reporter` integration are no longer part of 2.x.
-- **Configuration filename scope.** In 2.x, plugin discovery/generation/migration is centered on `cucumber.js`.
+- **All cucumber-js config formats.** Plugin discovery, generation, and migration support every cucumber-js configuration file format (`cucumber.js`, `.cjs`, `.mjs`, `.ts`, `.mts`, `.cts`, `.json`, `.yaml`, `.yml`). See [Config file formats](#config-file-formats).
 
 ## Prerequisites
 
@@ -229,7 +231,11 @@ Target names can be customized:
 
 ### Cucumber configuration
 
-All Cucumber options are configured in the `cucumber.js` file. The generator creates a default configuration. For example, to customize tags based on environment variables:
+The generator scaffolds a cucumber-js configuration file for each project. It is a standard cucumber-js config, so any advanced Cucumber [option](https://github.com/cucumber/cucumber-js/blob/main/docs/configuration.md#options) can be set there.
+
+#### Default configuration
+
+By default the generator creates a `cucumber.js`. Because the code formats are evaluated when loaded, options can be computed at runtime — for example, deriving the tag filter from an environment variable:
 
 ```javascript
 const tagsFilter =
@@ -244,9 +250,78 @@ module.exports = {
 };
 ```
 
-All advanced Cucumber [options](https://github.com/cucumber/cucumber-js/blob/main/docs/configuration.md#options) can be set in the `cucumber.js` file.
+#### Config file formats
+
+Nx-cucumber supports every cucumber-js configuration file format for inferred-task discovery, generator output, and migration output. Select one with the generator's `configFormat` option (default `js`):
+
+| `configFormat` | Config file     | Style    |
+| -------------- | --------------- | -------- |
+| `js` (default) | `cucumber.js`   | CommonJS |
+| `cjs`          | `cucumber.cjs`  | CommonJS |
+| `mjs`          | `cucumber.mjs`  | ESM      |
+| `ts`           | `cucumber.ts`   | ESM / TS |
+| `mts`          | `cucumber.mts`  | ESM / TS |
+| `cts`          | `cucumber.cts`  | ESM / TS |
+| `json`         | `cucumber.json` | JSON     |
+| `yaml`         | `cucumber.yaml` | YAML     |
+| `yml`          | `cucumber.yml`  | YAML     |
+
+The **code formats** (`js`, `cjs`, `mjs`, `ts`, `mts`, `cts`) are evaluated as modules, so they can contain logic like the default configuration above. The **data formats** (`json`, `yaml`, `yml`) are static and hold plain values only.
+
+The same configuration expressed in the remaining formats:
+
+**ES module** — `cucumber.mjs`
+
+```javascript
+const tagsFilter =
+  process.env['CI_STAGE'] !== 'qa'
+    ? 'and not @qa-stage-only'
+    : 'and (@qa-stage or @qa-stage-only)';
+
+export default {
+  default: {
+    tags: `not @ignore ${tagsFilter}`,
+  },
+};
+```
+
+**TypeScript** — `cucumber.ts`, `cucumber.mts`, `cucumber.cts`
+
+```typescript
+import type { IConfiguration } from '@cucumber/cucumber';
+
+const tagsFilter =
+  process.env['CI_STAGE'] !== 'qa'
+    ? 'and not @qa-stage-only'
+    : 'and (@qa-stage or @qa-stage-only)';
+
+const config: { default: Partial<IConfiguration> } = {
+  default: {
+    tags: `not @ignore ${tagsFilter}`,
+  },
+};
+
+export default config;
+```
+
+**JSON** — `cucumber.json`
+
+JSON is static and cannot run the environment check above, so the tags are set directly:
 
-> **2.x limitation:** `@gnuechtel/nx-cucumber` currently supports `cucumber.js` as the plugin configuration file for inferred-task discovery, generator output, and migration output. Other Cucumber config filenames (for example `cucumber.mjs`) are not supported by the plugin in this major version.
+```json
+{
+  "default": {
+    "tags": "not @ignore"
+  }
+}
+```
+
+**YAML** — `cucumber.yaml`, `cucumber.yml`
+
+```yaml
+default:
+  tags: 'not @ignore'
+```
 
 ### World parameters
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gnuechtel/nx-cucumber",
-  "version": "2.1.0",
+  "version": "2.1.1",
   "description": "Plugin to use Cucumber within Nx workspaces",
   "license": "MIT",
   "repository": {
@@ -12,8 +12,8 @@
     "@nx/devkit": ">=22 <23",
     "minimatch": "^10.0.0",
     "tslib": "^2.3.0",
-    "@gnuechtel/shared-coverage": "2.1.0",
-    "@gnuechtel/shared-util": "2.1.0"
+    "@gnuechtel/shared-coverage": "2.1.1",
+    "@gnuechtel/shared-util": "2.1.1"
   },
   "peerDependencies": {
     "@cucumber/cucumber": ">=9 <13",