Github Actions - Error: can't find the configuration file located at ${rawConfigPath}.

_sadajo_last year

5

 Caused by:
    unknown field `cwd` at line 1 column 3195
/home/runner/work/{{repo_name}}/{{repo_name}}/node_modules/payload/dist/bin/build.js:35
        throw new Error(`Error: can't find the configuration file located at ${rawConfigPath}.`);

Error: Error: can't find the configuration file located at /home/runner/work/{{repo_name}}/{{repo_name}}/apps/cms/src/payload.config.ts.

• 

  jmikrut

  last year

  yes i wouldn't trust that error

  
  
  

  i actually added a fix to our roadmap to clarify error messages that come from the admin build process earlier today

  
  
  

  i dont know why this would be, but maybe Github Actions don't allow the use of

  process.cwd

  ?

• 

  _sadajo_last year

  I'm at a bit of a loss on how to debug this one. The error output isn't very descriptive so I'm not sure which file or dependency is throwing it. The post was for 1.8.2, and I upgraded to 1.8.5. The only thing that changed was the column number

  
  
  

  unknown field `cwd` at line 1 column 4148

  
  
  

  Going to make sure it's not something in my specific setup by trying a fresh version of payload

  
  
  

  I found the problem. I grepped the error message to find out where that string originated from and it was in an SWC .node binary file.

  
  
  

  I'm running payload in an NX monorepo and had the following dependency:

  
  "@swc/core": "~1.3.51"
  
  

  After upgrading it to the latest 1.3.62, it successfully ran in the github actions runner

  
  
  

  I suppose there was a bug in that version

• 

  jmikrut

  last year

  Woah!

  
  
  

  Nice work!! Thanks for reporting the fix that you found as well

• 

  richadrlast year

  just to add this for people landing through search, I traced it down to this specific issue

  
  https://github.com/swc-project/swc/issues/5616#issuecomment-1551706075
  

  for me, it would run fine locally but fail in GitHub Actions. i updated pipeline and added this hack after

  npm ci

  :

  
  npm i --no-save @swc/core
• 

  wkd1079last year

  thank you OP, i hit a similar issue yesterday and had been totally stumped. commands also work fine locally, and in docker, but choke in GH actions (and using

  act

  to test actions locally). the error message also made me wonder if my monorepo architecture was a contributing factor... 🤔

  
  
  

  like many other commenters in the swc thread, I sidestepped the issue by using

  pnpm

  for this specific command, rather than

  npm

  which I use everywhere else. not ideal but it works.

  
  
  

  unlike OP, I do not have a direct

  swc

  dependency that I can adjust to fix the issue. instead, i'm relying on payload's, which I noticed are deprecated:

  https://github.com/payloadcms/payload/blob/b8cd1c6ba44cda2baa9b08fea09e69580ebe7a1a/package.json#L42-L44
  
  

  I wonder if migrating from

  @swc/*

  to

  @swc-node/*

  would fix this for good. i will do some more testing and open a PR when i have a chance!