feat: add ability to output bundles in separate directory#4841
feat: add ability to output bundles in separate directory#4841ValeryVS wants to merge 1 commit intoangular:masterfrom
Conversation
86e2538 to
374c210
Compare
|
There are errors with deploy test. |
374c210 to
ac7d692
Compare
ac7d692 to
83854a2
Compare
|
@filipesilva could you see this |
|
Heya @ValeryVS, I'm not sure we want to add this option... It's very similar to the existing I think you raise a good point about EOT files. You can do it currently via |
|
I will research about |
|
I see... |
|
@ValeryVS how were you able to use deployUrl with moving the bundle files? I'm attempting to achieve this with mkdir dist/static && find dist -type f -maxdepth 1 -mindepth 1 -not -name index.html -exec mv '{}' dist/static \;which seems to mostly work, however some of the links are broken as I have a separate asset directory, but setting the |
|
.angular-cli.sjon {
"deployUrl": "app/"
}makefile or shell script mv dist dist-tmp
mkdir dist
mv dist-tmp dist/app
mv dist/app/index.html dist/Result |
|
@ValeryVS thanks, I was able to work it out, turns out I was having issue with the base root definitions in my scss files, eg I had to change Saying that, I still think this should be an Angular CLI feature, as it is probably a very common use case to have your webserver redirect all requests to |
|
@zakhenry |
|
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. |
Implements #4788
Add
bundlesOutDiroption to.angular-cli.json