Scrripts gen:types or gen:importmap do not run if type is not module inside package.json

[HQ92]

Describe the Bug

I have a use-case where I am running a payload admin panel inside a nextjs project with a babel.config.js as I am using StyleX which does not work with SWC at the moment. Removing type="module" from the package file causes payload commands to fail. But adding it causes nextjs to fail because it cannot import babel.config because internally it uses require to load in custom babel.configs.

Is there a way to get payload commands to run without type='module', or some way to get the project to work with a custom babel.config with type='module'?

Link to the code that reproduces this issue

Any new payload v3 project, remove, type='module', add simple babel.config.js to root.

Reproduction Steps

1. Create new starter Payload v3 project.
2. Add custom babel.config.js, with the simplest config.
3. Remove type='module'
4. Try to run gen:types or gen:importmap
5. Will fail

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

area: core

Environment Info

Payload: v3.2.1
Node: v21.1.0
Nextjs: 15.0.3

[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