Join GitHub today
Webpack fails only when run through `npm run` command #12931
Ok I've been pulling my hair out on this issue all day thinking that it was something I have done incorrectly (this could still be the case). If I run
Please note that this is running on Azure Websites (kudu) The command works fine on my local machine.
Output when run using
Output when run straight from the Powershell console on Kudu:
Running into a similar issue
referenced this issue
Jun 3, 2016
@deevus I have spent more than 3 days trying to debug this issue to no avail, but in the end I removed
Let me know if a global webpack package solves the issue so I can get a closure with this bug.
@deevus I suspect that the problem is inside webpack's
Here is a gist of callstack I've got: https://gist.githubusercontent.com/zygimantas/6d5fcb15547e84f5773f7b6226734737/raw/f37bd1a1ee46018413aa4cb24fc6187732314838/output.txt
And here is a not very well formulated stackoverflow question: http://stackoverflow.com/questions/38173996/azure-and-node-js-dirname
I tried debugging the normalize.js file and it was stuck in recursion with path
EDIT: There's good info in the SO question @zygimantas posted http://stackoverflow.com/questions/38173996/azure-and-node-js-dirname. Downgrading to 5.9.0 worked for me.