Build error paths: How to interpret


#1

I’m trying to find out why a build s not working. The console output is a call stack with lots of .js files with line number references.

at require                                                                 │
(packages/modules-runtime/.npm/package/node_modules/install/install.js:82:1│  PID USER      PR  NI    VIRT    RES  %CPU %MEM     TIME+ S COMMAND       
)                                                                          │    1 root      20   0  132.6m   2.0m   0.0  0.1   0:03.02 S systemd       
at new ScssProcessor (packages/mss/scss-processor.js:12:55)                │  188 root      20   0  168.7m  13.3m   0.0  0.3   0:01.42 S  `- systemd-+ 
at CssModulesBuildPlugin._setupPreprocessors                               │  222 root      20   0   35.8m   2.1m   0.0  0.1   0:00.41 S  `- systemd-+ 
(packages/mss/css-modules-build-plugin.js:104:31)                          │  339 root      20   0   37.6m   0.8m   0.0  0.0   0:00.36 S  `- systemd-+ 
at CssModulesBuildPlugin.processFilesForTarget                             │  340 dbus      20   0   32.9m   1.9m   0.0  0.1   0:03.72 S  `- dbus-dae+ 
(packages/mss/css-modules-build-plugin.js:53:10)

However, none of these files seem to exist on my disk… The build is breaking in a plugin. Does anybody have any pointers to any documentation on how the build process works? Why are these files listed? Is it something like bundeled libraries with javascript? (Like .so or .dll)? Since JavaScript is not compiled, I didn’t think there would be.

Thank you, any help appreciated.