Ideas for Arc XP

Document Site Styles Config for Fusion 3.3

When running Fusion locally with 3.3 on startup this error is thrown:

fusion-webpack | Error: ENOENT: no such file or directory, scandir '/opt/engine/bundle/src/site-styles'

fusion-webpack | at Object.readdirSync (fs.js:1047:3)

fusion-webpack | at Object.<anonymous> (/opt/engine/webpack/styles/index.js:24:31)

fusion-webpack | at Module._compile (internal/modules/cjs/loader.js:1085:14)

fusion-webpack | at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)

fusion-webpack | at Module.load (internal/modules/cjs/loader.js:950:32)

fusion-webpack | at Function.Module._load (internal/modules/cjs/loader.js:790:12)

fusion-webpack | at Function.Module._load (/opt/engine/node_modules/mock-require/index.js:30:22)

fusion-webpack | at Module.require (internal/modules/cjs/loader.js:974:19)

fusion-webpack | at require (internal/modules/cjs/helpers.js:93:18)

fusion-webpack | at Object.<anonymous> (/opt/engine/webpack/index.js:7:3)

fusion-webpack | at Module._compile (internal/modules/cjs/loader.js:1085:14)

fusion-webpack | at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)

fusion-webpack | at Module.load (internal/modules/cjs/loader.js:950:32)

fusion-webpack | at Function.Module._load (internal/modules/cjs/loader.js:790:12)

fusion-webpack | at Function.Module._load (/opt/engine/node_modules/mock-require/index.js:30:22)

fusion-webpack | at Module.require (internal/modules/cjs/loader.js:974:19) {

fusion-webpack | errno: -2,

fusion-webpack | syscall: 'scandir',

fusion-webpack | code: 'ENOENT',

fusion-webpack | path: '/opt/engine/bundle/src/site-styles'

fusion-webpack | }


We are not using multi-site. Are there files that need to be added somewhere>

  • Spencer Beggs
  • May 19 2022
  • Planned
  • Attach files
  • Admin
    Fatih Yildiz commented
    19 May 09:14pm

    Hi Spencer,


    Thanks for reporting this.


    I've checked with the team and we confirmed that this is just a warning on the compiler. It shouldn't stop the compiler to finish successfully. This is a warning rather than ERROR. Although the exception is surfaced with the full stack trace in compiler logs, I totally see this can be confusing or can create anxiety for developers. I'm coordinating this with the team on the upcoming patch or release to update this case with a softer warning message rather than an error stack trace.