Grunt 1.6.1 async task handling with Node.js 18+

Goal

Determine how to keep custom Grunt tasks functioning when running on Node.js 18+ while respecting the legacy this.async() contract.

Constraints

• Grunt 1.6.1 core relies on the this.async() callback pattern; it does not natively accept Promise returns.
• Node.js 18+ emits unhandled rejection warnings for Promise-based code that is not awaited or caught, which can surface during CI pipelines.
• Many community plugins have not been updated for Node 18+ changes (e.g., stricter crypto module behavior), leading to runtime warnings or failures.
• No official Grunt 2.x release or roadmap exists to modernize async APIs.

Unresolved Decision

Should developers wrap Promise logic inside this.async() callbacks, adopt a community wrapper, or migrate to a different build tool for new projects?

Questions

1. What patterns are currently recommended for integrating async/await into Grunt 1.6.1 tasks when targeting Node.js 18+?
2. How can we suppress or handle the unhandled rejection warnings that arise from Promise-based plugin code?
3. Is there an officially supported or widely adopted wrapper that preserves this.async() semantics while allowing Promise returns?