Why does `payload.init` still require the config path to be set via env when `config` is supplied? | Payload | Page 1

frank galleon Feb 24, 2023, 9:31 AM

#

I want to use the payload package in a monorepo, where our app creates a payload instance in local mode and supplies config during init, but it still errors saying it needs to find the config file. Why? Surely providing the config should remove the requirement on reading the config file from disk?

rough zenith Mar 6, 2023, 12:50 PM

#

Hi @frank galleon - is your payload config being added in the same location? https://payloadcms.com/docs/configuration/overview#customizing-and-overriding-the-config-location

Payload CMS

The Payload Config | Documentation | Payload CMS

The Payload config is central to everything that Payload does, from adding custom React components, to modifying collections, controlling localization and much more.

left hamlet Mar 6, 2023, 3:12 PM

#

I think the OP's question was more about, if we can pass the Payload config object directly to the payload init, why do we need to specify the path at all?

#Why does `payload.init` still require the config path to be set via env when `config` is supplied?