We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ ] Regression [X] Bug report [ ] Feature request [X] Documentation issue or request [X] Support request
After i run ng eject my current full folder path is being hardcoded in the webpack build
ng eject
... new CircularDependencyPlugin({ "exclude": /(\\|\/)node_modules(\\|\/)/, "failOnError": false, "onDetected": false, "cwd": "D:\\Users\\sarbull\\projects\\angularApp" }), ...
Should have been a relative path?
Run ng eject check the webpack.config.js on line 406 in the CircularDependencyPlugin.
webpack.config.js
If i move the application in another folder will result in different folder paths.
The text was updated successfully, but these errors were encountered:
Fixed in #9346.
Sorry, something went wrong.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
No branches or pull requests
I'm submitting a...
Current behavior
After i run
ng eject
my current full folder path is being hardcoded in the webpack buildExpected behavior
Should have been a relative path?
Minimal reproduction of the problem with instructions
Run
ng eject
check thewebpack.config.js
on line 406 in the CircularDependencyPlugin.What is the motivation / use case for changing the behavior?
If i move the application in another folder will result in different folder paths.
The text was updated successfully, but these errors were encountered: