x)
Yes, the previous version in which this bug was not present was: no idea
Still browser is able to cache my JS changes in production too. You will have to clear cache with ctrl + shift + r.
angular.json
"production": {
"budgets": [
{
"type": "anyComponentStyle",
"maximumWarning": "6kb"
}
],
"optimization": true,
"outputHashing": "all",
"sourceMap": false,
"extractCss": true,
"namedChunks": false,
"aot": true,
"extractLicenses": true,
"vendorChunk": false,
"buildOptimizer": true,
"fileReplacements": [
{
"replace": "src/environments/environment.ts",
"with": "src/environments/environment.prod.ts"
}
]
},
ng version
Your global Angular CLI version (9.1.1) is greater than your local
version (9.0.3). The local Angular CLI version is used.
To disable this warning use "ng config -g cli.warnings.versionMismatch false".
_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ β³ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 9.0.3
Node: 10.16.3
OS: win32 x64
Angular: 9.0.2
... animations, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router
Ivy Workspace: Yes
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.900.3
@angular-devkit/build-angular 0.900.3
@angular-devkit/build-optimizer 0.900.3
@angular-devkit/build-webpack 0.900.3
@angular-devkit/core 9.0.3
@angular-devkit/schematics 9.0.3
@angular/cdk 8.2.3
@angular/cli 9.0.3
@angular/material 8.2.3
@ngtools/webpack 9.0.3
@schematics/angular 9.0.3
@schematics/update 0.900.3
rxjs 6.5.4
typescript 3.7.5
webpack 4.41.2
Anything else relevant?
Hi @indraraj26, my two cents would be that the index.html is cached which in such case is more of a server configuration rather than an Angular CLI issue.
Unfortunately, there isnβt much information in this issue to validate if this is the real issue or not.
I will share website link tmrw it is hosted on aws s3 bucket. btw from where i can start to troubleshoot. how can i blame server team, it is an server side issue.
Let's not play the blame game π.
You can try to checking what the response for the index.html is and verify if that's the cached version or not.
For additional information on server cache settings, this article may be useful: https://web.dev/http-cache/
The Cache-Control header should typically be set to no-cache for the index.html. This can be checked in the dev tool's network tab of the browser.
Thank Alan and clydin for quick response on this. I will check this in morning and will update accordingly.
Hello,
Since Angular 7 i get this error: Unknown option: '--output-hashing'
What would be the right way to use this option ?
Thank you
Hello,
Since Angular 7 i get this error: Unknown option: '--output-hashing'What would be the right way to use this option ?
Thank you
β-output-hashing is a build option. See: https://angular.io/cli/build
@indraraj26, shall we close this?
Thank you for patience and i am really sorry for late response on this. yes i am closing since server team is looking into that.
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._
Most helpful comment
Let's not play the blame game π.
You can try to checking what the response for the
index.htmlis and verify if that's the cached version or not.