Request for Guidance on Deno Template Removal

[zkdiff]

Note: If the removal of the Deno template is transient, please disregard this issue—I understand changes like this happen during early/rapid/active development.

The Deno template for @remix-run/react-router-templates was recently created and then removed. I would like to understand the implications of this change for developers who may have been interested in using the template.

I'm seeking clarification on the following points, as it is unclear what the removal signals:

• Is Deno v2 an officially supported target runtime/platform for RR v7?
• Is a separate template no longer warranted due to Deno v2's Node.js compatibility improvements?
• If I'd like to get started using RR v7 on Deno, where would you recommend I start?

Please let me know if additional information would help in addressing this issue.

Additional Context

Any insight or future roadmap details regarding Deno support would be greatly appreciated.

I'm also interested in contributing to the Deno template to help reintroduce or maintain support, if that would be helpful.

[redabacha]

yeah this would be much appreciated knowing the remix's team stance on Deno v2 support. i've made a working template for RR v7 + Deno v2 based on the templates here (it uses typescript type checker for the app directory because Deno doesn't support rootDirs yet): https://github.com/redabacha/react-router-deno-template/. however it would be nice to see it officially supported.

[brookslybrand]

Hey sorry this hasn't received any attention. The team definitely wants to have a Deno template. We deleted it because the deploy didn't work properly, and unfortunately we haven't had time to work on it since then.

@redabacha if your template is similar to the existing ones/the one we originally had, please definitely feel free to open up a PR and I'll try to get it in