JoshuaKGoldberg / JoshuaKGoldberg/dot-com

🚀 Feature: Blog post on why I don't think TypeScript should type error on floating Promises

Open
#370 0 comments 0 reactions 1 assignee Claimed by @JoshuaKGoldberg View on GitHub
status: accepting prs type: feature
Dominant language
MDX
Stars
39
Forks
12
PR merge metrics
No merged PRs in 30d

Description

### Bug Report Checklist

- [x] I have tried restarting my IDE and the issue persists.
- [x] I have pulled the latest `main` branch of the repository.
- [x] I have [searched for related issues](https://github.com/JoshuaKGoldberg/dot-com/issues?q=is%3Aissue) and found none that matched my issue.

### Overview

This comes up a lot: e.g. https://x.com/kentcdodds/status/1888282003839307973 (just as a recent example). But I really don't think TypeScript should - the JS community oftentimes makes "fire-and-forget" Promises.

### Additional Info

See https://github.com/typescript-eslint/typescript-eslint/issues/10666 for links to other discussions on this.

💖

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.