VS Code launch.json config in a monorepo (Incorrect Webpack config.entry in monorepo setup)

ingrid7412 years ago

4

(root)
  package.json
  /packages
    /frontend-app1
    /frontend-app2
    /payload
      package.json
      /dist
        /src
          /payload-cms
          /vipps
          server.js
          ...
      /src
        /payload-cms
        /vipps
        server.ts
        payload.config.ts
        ...

ERROR in main
Module not found: Error: Can't resolve 'C:\_repos\multitenant-1\payload\dist\admin' in 'C:\_repos\multitenant-1'

Webpack Entry: {main: Array(2)}
  arg1: {main: Array(2)}
    main: (2) ['C:\\_repos\\multitenant-1\\node_modules\\webpack-hot-middleware\\client.js?path=/admin/__webpack_hmr', 'C:\\_repos\\multitenant-1\\payload\\dist\\admin']
      0: 'C:\\_repos\\multitenant-1\\node_modules\\webpack-hot-middleware\\client.js?path=/admin/__webpack_hmr'
      1: 'C:\\_repos\\multitenant-1\\payload\\dist\\admin'
      length: 2

export default buildConfig({
  admin: {
    bundler: webpackBundler(),
    webpack: config => {
      console.log('Webpack Entry:', config.entry)
      console.log('Webpack Resolve:', config.resolve)
      return { ...config }
    }
  },
...

• 

  stefvw932 years ago

  hey

  @735059082293149777

  did you find a solution? I have the same problem.

• 

  ingrid7412 years ago

  Hey. I encountered this when running a debugger in VS Code on built code. I abandoned it (still haven't got up the debugger), so nope nothing yet. But I've been able to build and serve the project since so I'll be looking into it again in a minute, will let you know if I find anything.

• 

  stefvw932 years ago

  Alright, thanks for your swift reply! Someone in my dev team decided to intermediately compile our monorepo packages which are used by Payload.

  
  
  

  Our structure is something like this:

  
  
  

  apps/some-website (nextjs)

  
  

  apps/payload-cms

  
  

  packages/lib (some utilities, typescript)

  
  

  packages/some-other-stuff

  
  
  

  All of our /packages are in typescript, and did not contain any kind of distribution build or likewise. They were just directly imported into our apps through module

  import

  s, and we never had the need for pre-built packages. But since payload is first only transpiled into JS, this broke our work flow.

  
  
  

  As an intermediate solution we now use

  tsup

  to quickly build our packages/lib, so it can be used by our apps/payload-cms dist build.

  
  
  

  Finally we added

  "@monorepo/lib": "file:../../packages/lib",

  to apps/payload-cms/package.json so it is treated as a regular node module.

  
  
  

  Not the most elegant solution but for right now this works for us.

• 

  ingrid7412 years ago

  TYSM for the pointers, the transpilation thing could very well be related to the issues I was seeing.

  
  
  

  The project was able to build and start later though so weird that the debugger specifically broke it.

  
  
  

  I was able to get up a debugger for the dev files of my Payload app in my monorepo using this

  launch.json

  configuration (credit to the Payload team - sorry I can't remember who forwarded this):

  
  

      {
        "command": "yarn run dev",
        "name": "Dev Payload",
        "request": "launch",
        "type": "node-terminal",
        "cwd": "${workspaceFolder}/packages/payload/src/"
      }

  
  
  

  VS Code launch.json config in a monorepo (Incorrect Webpack config.entry in monorepo setup)