fix: Fix invalid usage of import.meta.dirname Update run.js

[mdqst]

Description

The code incorrectly uses import.meta.dirname to resolve the path to specs.json. However, import.meta.dirname does not exist in Node.js, leading to the error:

Cannot read property 'dirname' of undefined

This update replaces the invalid import.meta.dirname usage with the correct approach, combining path.dirname and import.meta.url. The updated logic ensures compatibility with Node.js and properly resolves the directory path.

Changes made

• Updated the default value for the spec option to:

  path.resolve(path.dirname(new URL(import.meta.url).pathname), 'specs.json')

Why this change is necessary

The previous implementation would fail in environments using native ES modules in Node.js. The corrected approach leverages import.meta.url, which is the proper method to determine the current file's location, and ensures that the directory resolution is handled accurately.

Testing

Tested the updated logic to confirm the path to specs.json resolves correctly in both standard Node.js environments and those using ES module syntax.

PR Checklist

• Tests
• Documentation
• Changeset entry (run npx changeset add)

[changeset-bot]

⚠️ No Changeset found

Latest commit: b23d4f8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Amxx]

import.meta.dirname is valid since node 20