Bug: ERR_UNSUPPORTED_ESM_URL_SCHEME for undefined steps

[yavulan]

Given

playwright.config.ts

import { defineConfig } from '@playwright/test';
import { defineBddConfig } from 'playwright-bdd';

const testDir = defineBddConfig({
    paths: ['sample.feature'],
    require: ['*.ts'],
});

export default defineConfig({
    testDir,
    reporter: 'html',
});

sample.feature

Feature: Home Page

    Scenario: Check title
        Given I am on home page
        Then I see in title "Playwright"

steps.ts

import { expect } from '@playwright/test';
import { createBdd } from 'playwright-bdd';

const { Given, When, Then } = createBdd();

Then('I see in title {string}', async ({ page }, keyword) => {
    await expect(page).toHaveTitle(new RegExp(keyword));
});

When

npx bddgen

Then

ERR_UNSUPPORTED_ESM_URL_SCHEME related to loadSnippetBuilder

Expected behavior

When I do have an undefined step, like Given I am on home page in this example, there shouldn't be an error. Or, at least, the error should contain human-readable message.

Environment

platform: win32
node: v18.16.0
playwright-bdd: v5.4.0
@playwright/test: v1.39.0
@cucumber/cucumber: v10.0.1
Playwright config file: playwright.config.ts

[vitalets]

Reproduced this bug, investigating.

[vitalets]

Fixed in dev, will be included in the nearest release.

Reference issues:

• Windows path with the --format option works in v7, is broken in v8 cucumber/cucumber-js#1920
• ES Module loading with abolute path fails on windows nodejs/node#31710

Thanks for bringing this up!

[vitalets]

Landed in 5.5.0