Did you forget to signal async completion?
Open
Nobody has claimed this yet.
cli
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 641
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 57
Description
Describe the bug
when I run "npm run build", console print "Did you forget to signal async completion?"
To Reproduce
Steps to reproduce the behavior:
- git clone
- npm install
- npm run build
Desktop (please complete the following information):
- OS: Mac OS Big Sur
- node: v8.12.0
- npm: 6.4.1
- npx: 6.4.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the problem with git clone, npm install, and npm run build using the reported macOS, Node v8.12.0, and npm 6.4.1 environment. Start with the build output and trace which build step emits “Did you forget to signal async completion?”. Done means npm run build completes without that warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100