You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move the __dirname + require("path").sep + __webpack_public_path__ part of code to options. For example, this code is breaking use case with NextJS (Goto Actual behavior section)
Expected Behavior / Situation
Create an option: prefixPath with default of __dirname + require("path").sep + __webpack_public_path__
Actual Behavior / Situation
Broken use case with NextJS
Error node-loader: /home/user/my-project/.next/server/vendor-chunks//_next/9f92b6e3c34a390e5737ac41938d7846.node: cannot open shared object file: No such file or directory
Modification Proposal
Move the
__dirname + require("path").sep + __webpack_public_path__
part of code tooptions
. For example, this code is breaking use case with NextJS (Goto Actual behavior section)Expected Behavior / Situation
Create an option: prefixPath with default of
__dirname + require("path").sep + __webpack_public_path__
Actual Behavior / Situation
Broken use case with NextJS
Should be for working correctly:
outputPath +
_next/9f92b6e3c34a390e5737ac41938d7846.node
Link to next-node-laoderBut this library doesn't expose the name option. This causes conflicts.
Please paste the results of
npx webpack-cli info
here, and mention other relevant informationThe text was updated successfully, but these errors were encountered: