Instructions for Deno

[vintprox]

Deno 2 is all hypey and mighty today, so I thought it would be only appropriate to suggest the instructions for Deno users. Since it's already an npm package and Deno 2 supports both Node.js and npm now, why not include an npx-like command for existing CLI?

$ deno run -A npm:community-health-files

-A flag should give all sufficient permissions (detected: env and write), Deno should be able to fetch your package and run standalone package. The only dependency here is Deno.

In fact, I've tested it today and it seems to be running normally:

$ deno run -A npm:community-health-files

==========================================
[❗] – Questions are mandatory
==========================================

❗ What is the repository owner's name?
➜ vintprox

··················································

❗ What is the project license? (e.g., MIT, Apache, GPL):
➜ ISC

··················································

❗ Whom would you like to assign the raised bugs to?
➜ vintprox

··················································

❗ Who should be assigned the enhancement requests?
➜ vintprox

··················································

❗ To whom would you like to assign the feature requests?
➜ vintprox

··················································

❗ Who will be responsible for addressing questions related to the project?
➜ vintprox

··················································

❗ What is your organization name?
➜ rickrollinc

··················································

❗ What is your social media URL to connect?
➜ doesntmatt.er

··················································

❗ Please provide the email address for developers and contributors to contact you:
➜ [email protected]

··················································

Please provide the GitHub username(s) for funding (comma separated) or leave blank if none:
➜

··················································

Enter the Patreon username for funding (leave blank if none):
➜

··················································

Enter the Tidelift package name (e.g., npm/package-name) for funding (leave blank if none):
➜

··················································

Enter any custom funding URLs (comma separated) or leave blank if none:
➜

⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆


Community health files setup has been done successfully! ✅


If you appreciate my efforts, please consider supporting me by ⭐ my repository on GitHub: https://github.com/lassiecoder/community-health-files


⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆⋆⋅☆⋅⋆

Result: created docs and .github directories with files inside them.

So, why no PR from me? Because I'm not yet sure if it fits this project. There is a matter of npm being everywhere in generated documents, and adding deno to this pile might be an overkill, unless there was some conditional that would confirm which package manager is preferred (deno/npm). But again, I may be overthinking things.

Anyway, feel free to add the command above into README or disregard idea entirely.