asyncapi
Complete Nunjuck and `ag` deprecation -> remove it
Nunjucks is deprecated: https://github.com/asyncapi/generator/issues/1255
ag cli is deprecated: https://github.com/asyncapi/generator/issues/1229
- all nunjuck code must be removed from
apps/generator - remove
apps/nunjucks-filtersand deprecate in npm - remove all
agrelated code - make sure react engine is now treated as default (meaning nobody have to point to it in the template config)
- lots of cleanup in docs - not just removal of specific nunjucks docs, but probably refactor of few existing docs
- introduce code or just clear dev guide that still supports local development for templates developers - so it is easy for them to run template through generation process without writing tests and making any hacks to be able to run it through AsyncAPI CLI
- work with AsyncAPI CLI maintainers as this is a MAJOR release, a breaking change and we need to know how to get in into CLI (CLI already supports 2 generator versions - this probably should change)
I'll work on it. Work must take place not sooner than November.
Doing it all in one PR might be hard. Might be a feature branch will be needed.
It is an advanced issue, actually beyond advanced but 🤷🏼 all must be done as one effort
Bounty Issue's service comment
Text labels: bounty/2025-Q4, bounty/advanced, bounty/coding
First assignment to regular contributors: 2025-09-19 00:00:00 UTC+12:00
End Of Life after: 2025-10-31 23:59:59 UTC-12:00
@asyncapi/bounty_team
The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.
Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.
it's complex task with lots of insider knowlege - typical issue for maintainers. I'm going to work on it
Following the expression of desire to work on this Bounty Issue, @derberg (githubID: 6995927) is an AsyncAPI Maintainer specified in the file https://github.com/asyncapi/community/blob/master/MAINTAINERS.yaml, so they fall under the first category in the prioritization list.
Bounty Issue's Timeline
| Complexity Level | Assignment Date (by GitHub) | Start Date (by BP Rules) | End Date (by BP Rules) | Draft PR Submission | Final PR Merge Start | Final PR Merge End |
|---|---|---|---|---|---|---|
| Advanced | 2025-09-16 | 2025-10-06 | 2025-11-30 | 2025-10-26 | 2025-11-16 | 2025-11-30 |
Please note that the dates given represent deadlines, not specific dates; so if the goal is reached sooner, it's better.
Keep in mind the responsibility for violations of the Timeline.
Assignee: @derberg (githubID: 6995927)
it is designed to be done later, as in description Work must take place not sooner than November
started working on this one.
first need this https://github.com/asyncapi/generator/pull/1754
Due to an active cybersecurity incident https://www.aikido.dev/blog/shai-hulud-strikes-again-hitting-zapier-ensdomains https://asyncapi.slack.com/archives/C34F2JV0U/p1763978529783109 https://github.com/asyncapi/website/pull/4640
which requires significant time and resources for immediate mitigation and lacks a clear timeframe for a final resolution that will prevent recurrence, the Timeline of this Bounty Issue is frozen for an indefinite amount of time.
PR submitter to reviewers
TODO afer merge:
- deprecate https://hub.docker.com/r/asyncapi/generator and point to CLI
- deprecate https://www.npmjs.com/package/@asyncapi/nunjucks-filters and point to release notes
This Bounty Issue is currently in its final stages, undergoing the final reviews.
in theory it is completed - only problem is that CLI releases are broken atm (escalated to NPM), so https://github.com/asyncapi/cli/pull/1919 was not released properly
I would suggest still waiting for the release and checking the released CLI's functionality to ensure this Bounty Issue is factually completed.