JoshuaKGoldberg / JoshuaKGoldberg/create-typescript-app

🚀 Feature: Create separate block for console-fail-test

Open
#2,306 0 comments 0 reactions 0 assignees View on GitHub
status: accepting prs type: feature
Dominant language
TypeScript
Stars
1.4k
Forks
89
Avg merge
1m
Merged PRs (30d)
3

Description

### Feature Request Checklist

- [x] I have looked at the latest version of the project.
- [x] I have [searched for related issues](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aissue) and found none that matched my issue.

### Overview

Right now, [`console-fail-test`](https://github.com/JoshuaKGoldberg/console-fail-test) is always included in `blockVitest`. No matter what. But some consumers might not want it:

* Not everyone wants to fully disable console calls in testing
* https://github.com/JoshuaKGoldberg/console-fail-test itself doesn't!

It'd be nice if a separate `blockConsoleFailTest` could be created.

### Additional Info

I prototyped this in #2308 but don't have bandwidth to investigate why the tests are failing.

🎁

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the existing blockVitest implementation and the prototype in issue #2308, then run the relevant test suite to investigate the reported failures. Done means console-fail-test can be configured through a separate blockConsoleFailTest instead of always being included in blockVitest.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
testing, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.