[mirek]

Summary

Changes the bare @nothrow directive to mute both its own line and the following line, so a single form works trailing a statement and on its own line above one:

throw new E(); // @nothrow     ← muted (trailing)

// @nothrow                    ← next line muted too
throw new E();

The explicit forms are unchanged and remain the way to target exactly one line:

• // @nothrow-line — only the directive's line
• // @nothrow-next-line — only the following line

One consequence worth knowing: a trailing bare @nothrow now also mutes the line below it. When that neighbouring line should stay checked, use @nothrow-line — the README calls this out, and a fixture covers the pitfall.

Packages bumped to 0.3.0.

Test plan

• pnpm run check green — build, oxlint, 10 core + 6 CLI tests
• New fixture cases: bare @nothrow above a throw (muted), @nothrow-line on its own line (next line still reported), trailing @nothrow-next-line (own line still reported), and the spill-over case in partiallyMuted
• Built CLI verified end-to-end on all three behaviours

🤖 Generated with Claude Code

https://claude.ai/code/session_01UG7WqvjcBWuMRj24ssFSrd

---

Generated by Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 33addab5b2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restrict bare @nothrow to directive comments

Because MUTE_DIRECTIVE matches @nothrow anywhere in any comment, adding directiveLine + 1 for every bare match makes prose comments silently suppress the following line. For example, a comment like // this API used to need @nothrow immediately above an exported function now mutes the function's missing-throws diagnostic even though it was not written as a directive, creating false negatives; consider only applying the next-line behavior when the comment body is actually a directive.

Useful? React with 👍 / 👎.

[Copilot]

Pull request overview

This PR updates the core analyzer’s @nothrow muting semantics so that the bare @nothrow directive mutes both its own line and the following line, allowing it to work consistently as either a trailing comment or as a standalone directive line.

Changes:

• Change collectMutedLines so bare @nothrow mutes both current and next line; explicit -line / -next-line remain single-target.
• Update docs/help text to reflect the new muting rules and the “spill-over” implication.
• Expand fixture + unit test coverage for the new behaviors and edge cases; bump package versions to 0.3.0.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
README.md	Documents bare vs explicit @nothrow* semantics and spill-over guidance.
packages/core/src/analyzer.ts	Implements updated muted-line collection rules for directives.
packages/core/test/mute-fix.test.ts	Adds assertions for new fixture cases under updated muting semantics.
packages/core/test/fixtures/muted.ts	Updates/extends fixture scenarios for bare and explicit directive behaviors.
packages/core/package.json	Bumps @throwscript/core version to 0.3.0.
packages/cli/src/main.ts	Updates CLI help text and printed version to 0.3.0.
packages/cli/package.json	Bumps CLI package version to 0.3.0.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.