Repository navigation
allowOutsideOutDir for assets not working again #9363
Description
Versions
Tested on:
1.6.3
1.6.5
Windows 10
Repro steps
-
npm install -G @angular/cli
-
cd to project with assets that need to be copied outside the project folder. From the .angular-cli.json:
"assets": [{
"input": "./assets/",
"glob": "**/*",
"output": "../EcView/WebContent/assets",
"allowOutsideOutDir": true
}], -
ng build
Observed behavior
Build failed:
>ng build
An asset cannot be written to a location outside the project.
Desired behavior
The build process copies the assets to the specified folder and completes the compilation of source code.
Other details
Seems similar to, possible regression of #8613
Activity
clydin commentedon Feb 7, 2018
@trendzetter Are you still experiencing this issue with 1.6.7?
trendzetter commentedon Feb 14, 2018
~~Issue no longer present in 1.6.8.~~~
I did not test correctly. The "allowOutsideOutDir" configuration was not present in the .angular-cli.json.
The issue is not resolved.
yuvalbl commentedon Apr 23, 2018
Angular version: 6.0.0-rc.5
Angular-CLI version: 6.0.0-rc.5
I've created a new project and was able to build to a directory outside the project root, with no allowOutsideOutDir flag
side-note:
If I get it correctly, .angular-cli.json configuration is now included in angular.json.
Repro steps:
'../MyDir'ng buildRelated to #9686
seems like this commit is the problem
filipesilva commentedon May 4, 2018
This option has been removed in Angular CLI 6. I now added a
Breaking Changessection to https://github.com/angular/angular-cli/releases/tag/v6.0.0, with this change listed, will also add a warning during the update process. This is being tracked in #10647.angular-automatic-lock-bot commentedon Sep 8, 2019
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.