Angular 6 template cache problem (for html files) on gulp build
We have template cache problem for html files and we would like to solve it without deleting the cache data(If we delete it, we see performance issue).
Do you have any suggestions for it ?
angular gulp angular-templatecache
edited Jan 3 at 0:38
benshabatnoam
1,9801121
asked Jan 1 at 13:45
Mustafa AkgureMustafa Akgure
127
add a comment |
We have template cache problem for html files and we would like to solve it without deleting the cache data(If we delete it, we see performance issue).
Do you have any suggestions for it ?
angular gulp angular-templatecache
edited Jan 3 at 0:38
benshabatnoam
1,9801121
asked Jan 1 at 13:45
Mustafa AkgureMustafa Akgure
127
Do you mean after deploying the app?
– benshabatnoam
Jan 1 at 14:19
Yes, we use yarn, gulp. Before deploying the app, we use ng build --prod plugins. It creates a hash files for resources. And the browser should be force to load new minimized resource files. But we face with template-cache problem and we have to delete browser cache to run it properly. This is really big problem for our users, can you give me some advice? What else can I do?
– Mustafa Akgure
Jan 2 at 10:43
add a comment |
We have template cache problem for html files and we would like to solve it without deleting the cache data(If we delete it, we see performance issue).
Do you have any suggestions for it ?
angular gulp angular-templatecache
edited Jan 3 at 0:38
benshabatnoam
1,9801121
asked Jan 1 at 13:45
Mustafa AkgureMustafa Akgure
127
We have template cache problem for html files and we would like to solve it without deleting the cache data(If we delete it, we see performance issue).
Do you have any suggestions for it ?
angular gulp angular-templatecache
angular gulp angular-templatecache
edited Jan 3 at 0:38
benshabatnoam
1,9801121
asked Jan 1 at 13:45
Mustafa AkgureMustafa Akgure
127
edited Jan 3 at 0:38
benshabatnoam
1,9801121
asked Jan 1 at 13:45
Mustafa AkgureMustafa Akgure
127
edited Jan 3 at 0:38
benshabatnoam
1,9801121
edited Jan 3 at 0:38
benshabatnoam
1,9801121
edited Jan 3 at 0:38
benshabatnoam
1,9801121
1,9801121
asked Jan 1 at 13:45
Mustafa AkgureMustafa Akgure
127
asked Jan 1 at 13:45
Mustafa AkgureMustafa Akgure
127
asked Jan 1 at 13:45
Mustafa AkgureMustafa Akgure
127
127
Do you mean after deploying the app?
– benshabatnoam
Jan 1 at 14:19
Yes, we use yarn, gulp. Before deploying the app, we use ng build --prod plugins. It creates a hash files for resources. And the browser should be force to load new minimized resource files. But we face with template-cache problem and we have to delete browser cache to run it properly. This is really big problem for our users, can you give me some advice? What else can I do?
– Mustafa Akgure
Jan 2 at 10:43
add a comment |
Do you mean after deploying the app?
– benshabatnoam
Jan 1 at 14:19
Yes, we use yarn, gulp. Before deploying the app, we use ng build --prod plugins. It creates a hash files for resources. And the browser should be force to load new minimized resource files. But we face with template-cache problem and we have to delete browser cache to run it properly. This is really big problem for our users, can you give me some advice? What else can I do?
– Mustafa Akgure
Jan 2 at 10:43
Do you mean after deploying the app?
– benshabatnoam
Jan 1 at 14:19
Do you mean after deploying the app?
– benshabatnoam
Jan 1 at 14:19
Yes, we use yarn, gulp. Before deploying the app, we use ng build --prod plugins. It creates a hash files for resources. And the browser should be force to load new minimized resource files. But we face with template-cache problem and we have to delete browser cache to run it properly. This is really big problem for our users, can you give me some advice? What else can I do?
– Mustafa Akgure
Jan 2 at 10:43
Yes, we use yarn, gulp. Before deploying the app, we use ng build --prod plugins. It creates a hash files for resources. And the browser should be force to load new minimized resource files. But we face with template-cache problem and we have to delete browser cache to run it properly. This is really big problem for our users, can you give me some advice? What else can I do?
– Mustafa Akgure
Jan 2 at 10:43
add a comment |
2 Answers
2
active
oldest
votes
One good solution for your problem is called file revision or Hashing, this approach concept is:
simply rename every html/js/img file served by our app by
concatenating a random-hash before the file extension
There are many possible ways doing that. One good way is this 3 steps:
Step 1. Creating revision:rename gulp task
gulp.task(“revision:rename”, [“compile”], () =>
gulp.src(["dist/**/*.html",
"dist/**/*.css",
"dist/**/*.js",
"dist/**/*.{jpg,png,jpeg,gif,svg}"])
.pipe(rev())
.pipe(revdel())
.pipe(gulp.dest(“dist”))
.pipe(rev.manifest({ path: “manifest.json” }))
.pipe(gulp.dest(“dist”))
);
Step 2. Creating revision:updateReferences gulp task
gulp.task(“revision:updateReferences”, [“compile”, “revision:rename”], () =>
gulp.src([“dist/manifest.json”,”dist/**/*.{html,json,css,js}”])
.pipe(collect())
.pipe(gulp.dest(“dist”))
);
Step 3. Creating compile:production gulp task
gulp.task(“compile:production”, [“compile”, “revision:rename”, “revision:updateReferences”]);
This 3 steps solution taken from:
medium.com - Solving Browser Cache Hell With Gulp-Rev - By Felipe
Bernardes
answered Jan 2 at 12:05
benshabatnoambenshabatnoam
1,9801121
add a comment |
Thanks for your answer, but our solution is little different. In our company, we use weblogic server and When we deploy the app, it creates all resources in specific folder and again and again(It holds previous ones). After deleting the unnecessary resources, the app start to work properly.
answered Jan 4 at 11:35
Mustafa AkgureMustafa Akgure
127
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53995958%2fangular-6-template-cache-problem-for-html-files-on-gulp-build%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
One good solution for your problem is called file revision or Hashing, this approach concept is:
simply rename every html/js/img file served by our app by
concatenating a random-hash before the file extension
There are many possible ways doing that. One good way is this 3 steps:
Step 1. Creating revision:rename gulp task
gulp.task(“revision:rename”, [“compile”], () =>
gulp.src(["dist/**/*.html",
"dist/**/*.css",
"dist/**/*.js",
"dist/**/*.{jpg,png,jpeg,gif,svg}"])
.pipe(rev())
.pipe(revdel())
.pipe(gulp.dest(“dist”))
.pipe(rev.manifest({ path: “manifest.json” }))
.pipe(gulp.dest(“dist”))
);
Step 2. Creating revision:updateReferences gulp task
gulp.task(“revision:updateReferences”, [“compile”, “revision:rename”], () =>
gulp.src([“dist/manifest.json”,”dist/**/*.{html,json,css,js}”])
.pipe(collect())
.pipe(gulp.dest(“dist”))
);
Step 3. Creating compile:production gulp task
gulp.task(“compile:production”, [“compile”, “revision:rename”, “revision:updateReferences”]);
This 3 steps solution taken from:
medium.com - Solving Browser Cache Hell With Gulp-Rev - By Felipe
Bernardes
answered Jan 2 at 12:05
benshabatnoambenshabatnoam
1,9801121
add a comment |
One good solution for your problem is called file revision or Hashing, this approach concept is:
simply rename every html/js/img file served by our app by
concatenating a random-hash before the file extension
There are many possible ways doing that. One good way is this 3 steps:
Step 1. Creating revision:rename gulp task
gulp.task(“revision:rename”, [“compile”], () =>
gulp.src(["dist/**/*.html",
"dist/**/*.css",
"dist/**/*.js",
"dist/**/*.{jpg,png,jpeg,gif,svg}"])
.pipe(rev())
.pipe(revdel())
.pipe(gulp.dest(“dist”))
.pipe(rev.manifest({ path: “manifest.json” }))
.pipe(gulp.dest(“dist”))
);
Step 2. Creating revision:updateReferences gulp task
gulp.task(“revision:updateReferences”, [“compile”, “revision:rename”], () =>
gulp.src([“dist/manifest.json”,”dist/**/*.{html,json,css,js}”])
.pipe(collect())
.pipe(gulp.dest(“dist”))
);
Step 3. Creating compile:production gulp task
gulp.task(“compile:production”, [“compile”, “revision:rename”, “revision:updateReferences”]);
This 3 steps solution taken from:
medium.com - Solving Browser Cache Hell With Gulp-Rev - By Felipe
Bernardes
answered Jan 2 at 12:05
benshabatnoambenshabatnoam
1,9801121
add a comment |
One good solution for your problem is called file revision or Hashing, this approach concept is:
simply rename every html/js/img file served by our app by
concatenating a random-hash before the file extension
There are many possible ways doing that. One good way is this 3 steps:
Step 1. Creating revision:rename gulp task
gulp.task(“revision:rename”, [“compile”], () =>
gulp.src(["dist/**/*.html",
"dist/**/*.css",
"dist/**/*.js",
"dist/**/*.{jpg,png,jpeg,gif,svg}"])
.pipe(rev())
.pipe(revdel())
.pipe(gulp.dest(“dist”))
.pipe(rev.manifest({ path: “manifest.json” }))
.pipe(gulp.dest(“dist”))
);
Step 2. Creating revision:updateReferences gulp task
gulp.task(“revision:updateReferences”, [“compile”, “revision:rename”], () =>
gulp.src([“dist/manifest.json”,”dist/**/*.{html,json,css,js}”])
.pipe(collect())
.pipe(gulp.dest(“dist”))
);
Step 3. Creating compile:production gulp task
gulp.task(“compile:production”, [“compile”, “revision:rename”, “revision:updateReferences”]);
This 3 steps solution taken from:
medium.com - Solving Browser Cache Hell With Gulp-Rev - By Felipe
Bernardes
answered Jan 2 at 12:05
benshabatnoambenshabatnoam
1,9801121
One good solution for your problem is called file revision or Hashing, this approach concept is:
simply rename every html/js/img file served by our app by
concatenating a random-hash before the file extension
There are many possible ways doing that. One good way is this 3 steps:
Step 1. Creating revision:rename gulp task
gulp.task(“revision:rename”, [“compile”], () =>
gulp.src(["dist/**/*.html",
"dist/**/*.css",
"dist/**/*.js",
"dist/**/*.{jpg,png,jpeg,gif,svg}"])
.pipe(rev())
.pipe(revdel())
.pipe(gulp.dest(“dist”))
.pipe(rev.manifest({ path: “manifest.json” }))
.pipe(gulp.dest(“dist”))
);
Step 2. Creating revision:updateReferences gulp task
gulp.task(“revision:updateReferences”, [“compile”, “revision:rename”], () =>
gulp.src([“dist/manifest.json”,”dist/**/*.{html,json,css,js}”])
.pipe(collect())
.pipe(gulp.dest(“dist”))
);
Step 3. Creating compile:production gulp task
gulp.task(“compile:production”, [“compile”, “revision:rename”, “revision:updateReferences”]);
This 3 steps solution taken from:
medium.com - Solving Browser Cache Hell With Gulp-Rev - By Felipe
Bernardes
answered Jan 2 at 12:05
benshabatnoambenshabatnoam
1,9801121
answered Jan 2 at 12:05
benshabatnoambenshabatnoam
1,9801121
answered Jan 2 at 12:05
benshabatnoambenshabatnoam
1,9801121
answered Jan 2 at 12:05
benshabatnoambenshabatnoam
1,9801121
1,9801121
add a comment |
add a comment |
Thanks for your answer, but our solution is little different. In our company, we use weblogic server and When we deploy the app, it creates all resources in specific folder and again and again(It holds previous ones). After deleting the unnecessary resources, the app start to work properly.
answered Jan 4 at 11:35
Mustafa AkgureMustafa Akgure
127
add a comment |
Thanks for your answer, but our solution is little different. In our company, we use weblogic server and When we deploy the app, it creates all resources in specific folder and again and again(It holds previous ones). After deleting the unnecessary resources, the app start to work properly.
answered Jan 4 at 11:35
Mustafa AkgureMustafa Akgure
127
add a comment |
Thanks for your answer, but our solution is little different. In our company, we use weblogic server and When we deploy the app, it creates all resources in specific folder and again and again(It holds previous ones). After deleting the unnecessary resources, the app start to work properly.
answered Jan 4 at 11:35
Mustafa AkgureMustafa Akgure
127
Thanks for your answer, but our solution is little different. In our company, we use weblogic server and When we deploy the app, it creates all resources in specific folder and again and again(It holds previous ones). After deleting the unnecessary resources, the app start to work properly.
answered Jan 4 at 11:35
Mustafa AkgureMustafa Akgure
127
answered Jan 4 at 11:35
Mustafa AkgureMustafa Akgure
127
answered Jan 4 at 11:35
Mustafa AkgureMustafa Akgure
127
answered Jan 4 at 11:35
Mustafa AkgureMustafa Akgure
127
127
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53995958%2fangular-6-template-cache-problem-for-html-files-on-gulp-build%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you mean after deploying the app?
– benshabatnoam
Jan 1 at 14:19
Yes, we use yarn, gulp. Before deploying the app, we use ng build --prod plugins. It creates a hash files for resources. And the browser should be force to load new minimized resource files. But we face with template-cache problem and we have to delete browser cache to run it properly. This is really big problem for our users, can you give me some advice? What else can I do?
– Mustafa Akgure
Jan 2 at 10:43