Creating a plugin from the template fails

[robotex82]

Describe the Bug

When following the documentation at https://payloadcms.com/docs/plugins/build-your-own and trying to create a new plugin from the template with the given command npx create-payload-app@latest -t plugin -n my-new-plugin the command fails with:

❯ npx create-payload-app@latest -t plugin -n multi-tenancy


┌   create-payload-app 
│
◇   ────────────────────────────────────────────╮
│                                               │
│  Welcome to Payload. Let's create a project!  │
│                                               │
├───────────────────────────────────────────────╯
│
■  'plugin' is not a valid template.
│
◇  Valid templates: blank, website

The expected output would be a success with a created plugin folder structure.

Any ideas?

Thanks in advance!

Link to the code that reproduces this issue

Reproduction Steps

Execute npx create-payload-app@latest -t plugin -n multi-tenancy. See it fail with:

❯ npx create-payload-app@latest -t plugin -n multi-tenancy


┌   create-payload-app 
│
◇   ────────────────────────────────────────────╮
│                                               │
│  Welcome to Payload. Let's create a project!  │
│                                               │
├───────────────────────────────────────────────╯
│
■  'plugin' is not a valid template.
│
◇  Valid templates: blank, website

Which area(s) are affected? (Select all that apply)

area: docs, plugin: other, area: core

Environment Info

Node.js: v22.12.0

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@beta -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload

[denolfe]

Thank you for bringing this up. We need to bring this back into create-payoad-app.

As of now, the plugin-template repo has a functioning version for 3.0 on the beta branch.