The babel.config.js is exposed, but refers to a source file not available about payload

[jmikrut]

Good call!

Just opened a PR to address this. We actually need the babel.config.js to remain as-is, exporting from the /src folder—to accomplish development, exactly how you mentioned.

So, instead of changing that file, we've added a new file called payload/babel. With the change in that PR, you can now access the Babel config by doing the following:

import { config } from 'payload/babel'; 

How's that? We are going to be deploying a bunch of new stuff either later tonight or tomorrow - and this is definitely doable within that release!

[Ontopic]

Awesome! Just writing a reply in the discussion about module aliases (#201) that that is exactly what is needed for doing it through Babel in I feel a clean and stable enough way (also when upgrading NextJS or Payload). And... my import / require OCD is extra happy with it being a separately named payload/babel module, looks very pleasing next to next/babel 🙃

[github-actions]

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.