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
When ejecting a project with ng eject it generates/shows the Webpack configuration file using absolute paths. This makes it harder for collaboration, or creating functional examples, for cross-platform teams. In a project created, and ejected, on Windows I had to change the following lines, of the webpack.config.js, on macOS: 148, 151, 154, 187, 206, 233, 258, 284, 304, 332, 358, 396, 425, 491, 494.
Replace the existing absolute paths for relative ones. It could use path#join(or path#resolve), as some cases are using, to achieve that. Today, I'm solving this by changing it by hand.
The text was updated successfully, but these errors were encountered:
klauskpm
changed the title
Feature Request: replace absolute paths for relative ones on webpack when ejected
feat: replace absolute paths for relative ones on webpack when ejected
Mar 18, 2018
eject functionality is no longer available in the latest version (6.x+). For custom webpack configurations the following unofficial add-on is a suggested solution: https://github.com/manfredsteyer/ngx-build-plus
Versions
Observed behavior
When ejecting a project with
ng eject
it generates/shows the Webpack configuration file using absolute paths. This makes it harder for collaboration, or creating functional examples, for cross-platform teams. In a project created, and ejected, on Windows I had to change the following lines, of thewebpack.config.js
, on macOS: 148, 151, 154, 187, 206, 233, 258, 284, 304, 332, 358, 396, 425, 491, 494.Case
Example of project created on Windows
Example of project created on macOS
Desired behavior
Replace the existing absolute paths for relative ones. It could use
path#join
(orpath#resolve
), as some cases are using, to achieve that. Today, I'm solving this by changing it by hand.The text was updated successfully, but these errors were encountered: