Web project js css static file caching solution_html/css_WEB-ITnose

In the process of web development, we often encounter the problem of js and css file caching. During the development process, we can manually clear the browser cache ourselves, but we cannot tell users to perform a task that they may not be familiar with. Operation (clear browser cache), in order to solve this problem, a grunt plug-in was written. When building the front-end, you can use the grunt plug-in to do this, which is to automatically add a version number to the js and css files (here I use timestamps)

A plug-in based on grunt that automatically adds versions to js and css files. It can add a version number to all references in the configured directory to the specified matching js and css files

github address: https://github.com/noahxinhao/automatic-version-increment

Specific instructions

control the cache of assets by appending timestamp hash to asset url

Getting Started

This plugin requires Grunt ~0.4.1

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install automatic-version-increment --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('automatic-version-increment');

The "automatic" task

Overview

In your project's Gruntfile, add a section named automatic to the data object passed intogrunt.initConfig().

grunt.initConfig({    automatic: {      js: {        options: {        },        assetUrl:'demo/js/hello.js',        files: {          'tmp': ['demo/index.html'],        },      },    },});

Usage Examples

Default Options

In this example, we have index.html which contains hello.js and hello.css. In Gruntfile.js, write as below, then grunt, we can get the index.html which has assets url with timestamp.

assetUrl is the css or js file path files is the file which contains the assets(usually is html file)

Notice to write the correct path.

grunt.initConfig({    automatic: {            js: {                options: {                    basicSrc: ["src/main/webapp/public/js_control/"]                },                assetUrl: ['**/*.js'],                files: {                    'tmp': ['src/main/webapp/views/**/*.jsp']                }            },            css: {                options: {                    basicSrc: ["src/main/webapp/public/css/"]                },                assetUrl: ['**/*.css'],                files: {                    'tmp': ['src/main/webapp/views/**/*.jsp']                }            }        }});

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.