Pat Herlihy
Pat Herlihy
@evilebottnawi -- All set.
fix(webpack): Aliased module paths now properly map to the correct aurelia-loader module id [SIMPLE]
@jods4 I went ahead and rebased but I have yet to test it as I have not yet upgraded my own build to webpack 4. If you have a working...
fix(webpack): Aliased module paths now properly map to the correct aurelia-loader module id [SIMPLE]
@rek72 and @Alexander-Taran I have verified that this now works on both Windows, MacOS, and Linux using Webpack 4.
fix(webpack): Aliased module paths now properly map to the correct aurelia-loader module id [SIMPLE]
@jods4 I went ahead and re-based on `master`. Should be good to go.
fix(webpack): Aliased module paths now properly map to the correct aurelia-loader module id [SIMPLE]
@jods4 I went ahead and updated the PR, apologies on the delay. I commented with any questions I had and updated some things to conform to your style guide.
fix(webpack): Aliased module paths now properly map to the correct aurelia-loader module id [SIMPLE]
@jods4 Have you had a chance to review this yet?
fix(webpack): Aliased module paths now properly map to the correct aurelia-loader module id [SIMPLE]
Any update on this @jods4 @EisenbergEffect
fix(webpack): Aliased module paths now properly map to the correct aurelia-loader module id [SIMPLE]
@jods4 PR updated with changes. As for WHY this PR is needed, you can see the original PR #122. This PR is a simplified version of that which fixes the...
fix(webpack): Aliased module paths now properly map to the correct aurelia-loader module id [SIMPLE]
@jods4 The issue was aliases were never handled properly when mixed with relative/absolute paths. This new approach creates a mapping of all normalized paths and replaces the alias/relative/absolute path in...
Please try #139 and see if that fixes your issue.