fix(lib/getpluginname): preserve hyphenated anonymous plugin names

[lprnmns]

Problem

Anonymous plugins called from a hyphenated filename such as my-plugin.js are auto-named plugin-auto-N instead of my-plugin-auto-N. The filename parser only permits word characters and dots, so the valid basename is truncated.

Fix

Extract the complete basename from the stack frame, then remove only the line/column suffix and final extension. Existing dotted and Windows-style filename behavior remains covered.

Tests

• node --test test/extractPluginName.test.js — passed after the fix; the new assertion failed before the fix with actual plugin, expected my-plugin.
• npm test — passed; 45 unit tests, 3 type-test files, and 39 type assertions.
• npm run lint — passed.
• node --check lib/getPluginName.js && node --check test/extractPluginName.test.js — passed.
• git diff HEAD^ HEAD --check — passed.

Compatibility

This is a narrow parser correction with no public signature change. Existing dotted, Windows-style, no-match, explicit-name, and type-level paths were validated; no lockfile or generated files changed.

Related issue

Independent current reproduction; no open issue or competing PR was found. Historical issue #38 / PR #41 addressed dotted and TypeScript filename parsing; this change covers the remaining hyphenated basename case.

[Copilot]

🟢 Approval recommended

The parser correction is focused, backward-compatible with covered formats, and adequately tested.

Pull request overview

Fixes anonymous plugin-name extraction for hyphenated filenames while preserving existing dotted and Windows path behavior.

Changes:

• Reworks filename parsing to strip location suffixes and extensions.
• Adds regression coverage for my-plugin.js.

File summaries

File	Description
lib/getPluginName.js	Corrects basename extraction for hyphenated filenames.
test/extractPluginName.test.js	Adds the hyphenated-filename regression test.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Fdawgs]

Thanks for the PR, there's probably a nicer way of doing this using node:path's basename?

[lprnmns]

Updated as suggested: the extractor now uses node:path’s basename() and extname() after normalizing Windows separators, while preserving dotted filenames and the existing Windows/POSIX stack cases. I also merged current main to resolve the conflict without rewriting the reviewed history. Local validation: npm test passes (45 unit tests, 100% coverage, 39 TypeScript assertions) and npm run lint passes.

[Copilot]

🟢 Approval recommended

The focused parser fix is correct and adequately covered by existing and new tests.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0 new
• Review effort level: Balanced