Lifecycle Tasks
Open
Nobody has claimed this yet.
discussion
enhancement
v2
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
On top of Tasks API (#1974), we can support specific task prefixes init: (blocker), startup: (non-blocker), and close: that will be automatically called by nitro during startup and server close.
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
Read the Tasks API work in issue #1974 and locate the server startup and close entry points. Confirm that init:, startup:, and close: tasks are automatically invoked, with init: tasks blocking startup while startup: tasks do not, and that close tasks run during server shutdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100