test: run linting during npm test

[KJ7LNW]

Context

Run linting checks alongside tests to catch style and formatting issues before pushing code or creating PRs. This helps developers identify and fix issues earlier in their workflow.

Implementation

Modified scripts/run-tests.js to:

• Add lint:* to npm test command execution
• Maintain parallel execution on non-Windows systems

How to Test

1. Make a change that would fail linting (e.g. add trailing whitespace)
2. Run npm test
3. Verify that linting errors are reported alongside test results

Get in Touch

Discord: KJ7LNW

---

Important

Include linting in npm test command in scripts/run-tests.js to catch style issues early.

• Behavior:
  • Modifies scripts/run-tests.js to include lint:* in npm test command.
  • Ensures linting errors are reported alongside test results.
  • Maintains parallel execution on non-Windows systems.
• Testing:
  • To test, introduce a linting error and run npm test to verify error reporting.

^{This description was created by for dcf7bc7. You can customize this summary. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: dcf7bc7

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