I was wondering if its possible to get a configuration to define a webpack root(s) for file references. For example I am getting a stack trace with file references like:
' at processDBError (C:\project\bin\webpack:\core\lib\errorCodes.js:160:1)',
Here it is highlighting fully from C:\project all the way through to 160:1)',
So whenever I click the link naturally the file doesn't exist because its actual path is "C:\project\core\lib\errorCodes.js"
It would be nice if the console could detect via config any paths that are up to 'webpack:' then replace that with a defined root path to find the correct file location.
Additionally it shouldn't be adding the )', to the link.
Perhaps even to be more generic it would be nice to be able to just define an alternate path so a user can just map "C:\project\bin\webpack:" to "C:\project"
I was wondering if its possible to get a configuration to define a webpack root(s) for file references. For example I am getting a stack trace with file references like: ' at processDBError (C:\project\bin\webpack:\core\lib\errorCodes.js:160:1)', Here it is highlighting fully from C:\project all the way through to 160:1)', So whenever I click the link naturally the file doesn't exist because its actual path is "C:\project\core\lib\errorCodes.js"
It would be nice if the console could detect via config any paths that are up to 'webpack:' then replace that with a defined root path to find the correct file location.
Additionally it shouldn't be adding the )', to the link.
Perhaps even to be more generic it would be nice to be able to just define an alternate path so a user can just map "C:\project\bin\webpack:" to "C:\project"