@payloadcms/richtext-lexical: INSERT_UPLOAD_WITH_DRAWER_COMMAND is not publicly exported

[linesharina]

Describe the Bug

INSERT_UPLOAD_WITH_DRAWER_COMMAND exists internally in @payloadcms/richtext-lexical, but there is no supported public import path for it in the published package.

In @payloadcms/richtext-lexical@3.80.0:

• the package exports map does not expose the internal drawer command module
• @payloadcms/richtext-lexical/client does not re-export INSERT_UPLOAD_WITH_DRAWER_COMMAND

This makes it difficult to extend the upload drawer behavior from userland. The only working option I found is importing from a private built file under node_modules/@payloadcms/richtext-lexical/dist/..., which is brittle and couples app code to the package's internal layout.

Expected behavior:
INSERT_UPLOAD_WITH_DRAWER_COMMAND should be available from a supported public import path, ideally:

import { INSERT_UPLOAD_WITH_DRAWER_COMMAND } from '@payloadcms/richtext-lexical/client'

Link to the code that reproduces this issue

N/A - this issue is about a missing public export in the published package API, not a behavior bug with a standalone runtime reproduction.

Reproduction Steps

1. Install @payloadcms/richtext-lexical@3.80.0.
2. Check @payloadcms/richtext-lexical/client and confirm it does not export INSERT_UPLOAD_WITH_DRAWER_COMMAND.
3. Check the package contents and confirm the command exists internally at dist/features/upload/client/drawer/commands.js.
4. Confirm the package exports map does not expose that module as a public import path.

Which area(s) are affected?

plugin: richtext-lexical

Environment Info

Binaries:
  Node: 24.14.0
  npm: 11.9.0
  Yarn: 1.22.22
  pnpm: 9.6.0
Relevant Packages:
  payload: 3.80.0
  next: 16.2.1
  @payloadcms/db-postgres: 3.80.0
  @payloadcms/db-vercel-postgres: 3.80.0
  @payloadcms/drizzle: 3.80.0
  @payloadcms/email-nodemailer: 3.80.0
  @payloadcms/graphql: 3.80.0
  @payloadcms/live-preview: 3.80.0
  @payloadcms/live-preview-react: 3.80.0
  @payloadcms/next/utilities: 3.80.0
  @payloadcms/payload-cloud: 3.80.0
  @payloadcms/plugin-cloud-storage: 3.80.0
  @payloadcms/plugin-import-export: 3.80.0
  @payloadcms/plugin-multi-tenant: 3.80.0
  @payloadcms/plugin-seo: 3.80.0
  @payloadcms/richtext-lexical: 3.80.0
  @payloadcms/storage-vercel-blob: 3.80.0
  @payloadcms/translations: 3.80.0
  @payloadcms/typescript-plugin: 3.80.0
  @payloadcms/ui/shared: 3.80.0
  react: 19.2.4
  react-dom: 19.2.4
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.2.0: Tue Nov 18 21:09:45 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12

[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@latest -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