-
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
Provide config to rename index.html
in dist
folder
#2241
Comments
index.html
in dist
folderindex.html
in dist
folder
index.html
in dist
folderindex.html
in dist
folder
I think the existing config can be used for the output as well. This isn't a big priority, I want to be honest with you. There's just a lot of bigger fish to fry right now. But I can point you in the right direction in case you wanna do a PR.
|
Definitly need it too, and already have done something similar with my wepback config in an other project. |
Pass appConfig.index to the HtmlWebpackPlugin’s filename property. Closes angular#2241
Pass appConfig.index to the HtmlWebpackPlugin’s filename property. Closes angular#2241
Pass appConfig.index to the HtmlWebpackPlugin’s filename property. Closes angular#2241
PR created for publicPath support |
…3285) Add publicPath option for webpack. User can specify publicPath via `--deploy-url` / `-d` from command line or add `deployUrl` to `angular-cli.json`. It can solve following issues: Change the public URL address of the output files (different from baseUrl). Manipulate the request url for chunk js files. It is very helpful to solve resources url and route lazying load issues for those applications which have different static files paths such as ASP.NET MVC. Fixes #3136 Fixes #2960 Fixes #2276 Fixes #2241 Fixes #3344
Pass appConfig.index to the HtmlWebpackPlugin’s filename property. Closes angular#2241 Closes angular#2767
…ngular#3285) Add publicPath option for webpack. User can specify publicPath via `--deploy-url` / `-d` from command line or add `deployUrl` to `angular-cli.json`. It can solve following issues: Change the public URL address of the output files (different from baseUrl). Manipulate the request url for chunk js files. It is very helpful to solve resources url and route lazying load issues for those applications which have different static files paths such as ASP.NET MVC. Fixes angular#3136 Fixes angular#2960 Fixes angular#2276 Fixes angular#2241 Fixes angular#3344
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. |
This is a feature request.
Right now (beta-15), I can rename the source HTML file in
angular-cli.json
using theindex
property, but the output file indist
is still calledindex.html
.I don't care whether the implementation chooses to carry the name forward from the
index
property, or introduce another property for it.Use Case:
I need to use this inside an ASP .NET MVC application (.NET 4.5 not .NET Core).
My plan is to:
client
.client/dist
when it's not matching files / folders or APIsng build --watch
for dev, while IIS is looking at my parent server-side project folderBut I may well end up needing a legacy layout file, and some other server-side code to run before returning the HTML file, so my plan is to have a root server-side rout + MVC controller that returns the HTML file, using the Razor template engine (a
.cshtml
file, likeViews/Home/Index.cshtml
), which will still have the layout.But I still want Webpack to generate the
script
tag etc. So, I want to:index.html
filescript
tag etc, in the server-sideIndex.cshtml
file.But to include it in my server template, it's way easier for me if its extension was
cshtml
nothtml
. It's doable without that, but it's too much config, and part of this is showing the guys here how super easy it is to include Angular 2 seamlessly.P.S.
Sorry if this sounds like a very complex scenario, I believe it really isn't, and it's awesome to have something like this to integrate Angular 2 with server-side frameworks; and the change -I hope- isn't a big one really to support this.
Thanks a lot for creating such an awesome starter that makes developing Angular 2 much easier, and making it available for everyone for free, while you definitely do not have to, and owe nothing to any of us.
The text was updated successfully, but these errors were encountered: