-
Notifications
You must be signed in to change notification settings - Fork 12k
allowOutsideOutDir for assets not working again #9363
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
Comments
@trendzetter Are you still experiencing this issue with 1.6.7? |
~~Issue no longer present in 1.6.8.~~~ I did not test correctly. The "allowOutsideOutDir" configuration was not present in the .angular-cli.json. |
Angular 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: Repro steps:
Related to #9686 |
This option has been removed in Angular CLI 6. I now added a |
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
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:
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
The text was updated successfully, but these errors were encountered: