feat: pm-install generator

[cpreston321]

🔗 Linked issue

#5

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

# ✨ Auto-detect
npx nypm@latest add automd-playground

# npm
npm install automd-playground

# yarn
yarn add automd-playground

# pnpm
pnpm install automd-playground

# bun
bun install automd-playground

Args:
- name? (falls back to package.json "name")
- dev? (if true adds -D or --save-dev)
- auto? (if false remove nypm)

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

Do you mind to also add a new section to readme? 🙏🏼

[cpreston321]

@pi0 I added the changes for nypm.

[uncenter]

Would support for npx/bunx/pnpm dlx be a separate PR? Something like pm-run? Happy to implement that unless @cpreston321 wants to :)

[cpreston321]

Would support for npx/bunx/pnpm dlx be a separate PR? Something like pm-run? Happy to implement that unless @cpreston321 wants to :)

I would submit a new issue and talk to @pi0 about the feature!

[uncenter]

Thoughts on packages instead of name? I've often seen READMEs that suggest installing multiple at once (e.g. typescript-eslint suggests installing typescript as well).

For multiple, it could be a comma-separated (and space friendly) string:

    <!-- AUTOMD_START generator="pm-install" packages="package-name, other-package-name" dev="true" -->

    ```sh
    # npm
    npm install -D package-name other-package-name

    # yarn
    yarn add -D package-name other-package-name

    # pnpm
    pnpm install -D package-name other-package-name

    # bun
    bun install -D package-name other-package-name
    ```

    <!-- AUTOMD_END -->

And for a single one it would look the same but with a different key:

    <!-- AUTOMD_START generator="pm-install" packages="package-name" dev="true" -->

    ```sh
    # npm
    npm install -D package-name

    # yarn
    yarn add -D package-name

    # pnpm
    pnpm install -D package-name

    # bun
    bun install -D package-name
    ```

    <!-- AUTOMD_END -->

[pi0]

Hmm yes but it is also less common and I prefer to keep name shorter pm already suggests it is about package. We can easily also use name="pkg1 pkg2" btw even without array support wdyt?

[uncenter]

Well pm stands for "package manager" right? So it doesn't really suggest one way or another. How about we make it space separated though, you are right that comma-separated is a little much.

    <!-- AUTOMD_START generator="pm-install" packages="pkg1 pkg2" -->
    
    <!-- AUTOMD_START generator="pm-install" packages="pkg" -->

[pi0]

i read pm-install packages= as package manager install packages="..." while pm-install name= as package manger install name=.

More precisely what are setting in this param (according to npm) is "package specs"

Although we can really simply support packages as an alias if you strongly like it more feel free to make a new PR to propose (thinking to move this one forward faster)

[uncenter]

Sounds good yeah, I'll make a PR in the future!

[pi0]

Thank you both @cpreston321 and @uncenter for your contribution it was nothing I expected and happy having your collaborations ❤️

Mind you both automd and omark projects are really in trial stages and I usually used to keep projects like these private. So nothing in them is set in stone/ we don't need to worry about small details we can fix them later once main goals (like this generator) were met 👍🏼