-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
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
asset path must start with the project source root #10883
Comments
@juristr I think I know what happened here. Something in the project structure broke the paths when updating the It should be this instead:
Can you provide us with a reproduction of this problem happening? The old |
@filipesilva Sure, here's the original
|
Made a PR to fix this :) |
Did you manage to have it working? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Versions
Repro steps
I have a nrwl/nx repository which I migrated. The Angular CLI update script migrated my
.angular-cli.json
in the following way (excerpt of one of the projects in my monorepo):Note the assets configuration. If I try to build or serve this project I get the error
Changing the path from
to
doesn't work and results in this error:
What works is if I change it like this:
Observed behavior
(as described before in the repro steps)
Desired behavior
Although the "explicit" form of defining the assets paths works, the error message is very misleading and kinda strange, since my path is actually inside the project source root, especially when then changing it to
"assets": ["assets", "favicon.ico"],
Mention any other details that might be useful (optional)
This might be related to #10688 although it's not exactly the same use case.
//cc FYI @clydin
The text was updated successfully, but these errors were encountered: