Dev Helper

Dev Helper

Dev helper is all in one development and profiling extension for Google Chrome which has the following features: - Profiling webpages and drawing charts showing loading time for all assets, split by domain (including time till the first byte received) - Set up rewrite rules to override request and response urls, allowing developers to test without actually deploy new code. Developers could override, add or replace request and response headers to test different scenarios. For example adding 'Access-Control-Allow-Origin: *' in the response header section will resolve cross domain script blocking. Another way to use it is to replace asset or script (JavaScript and CSS) with local copy. This way the developer could make changes and test the functionality without deployment. 1.Install the extension from chrome app store. 2. Open page’s source code, and find the script tag, that you want to re-write. 3. Copy the code, and host it locally 4. Set up rewrite rule to load this file from your local web host Note, keep in mind that Match url is actually a regex so any regEx character should be escaped! For example if you want to match http://mysite.com/global.js?version=1 and redirect it to http://localhost?version=1 You could do this: Match url: http:\/\/mysite\.com\/global.js?(.*) Replacement URL: http://localhost?($1) The $1 will replace all query string parameters in the replacement url with these from the original url. - setting up rewrite rules to load assets from different locations. For example a developer could write a regular expression pattern to match all JavaScript files in particular website where he/she is working on, and load them from their local host. This way active development could be done in real time, and new features could be tested before deploying to production. This method is also useful to debug a production issues. example: if developer wants to test how the new code will affect the production website: http://www.mysite.com where all Java Script comes from: http://mysite.com/scripts/all_java_script.js file, they could write a rule that will match 'http://mysite.com/scripts/all_java_script.js' and load it from the localhost 'http://localhost/all_java_script.js' - Setting proxy rules that match different Regular expression patterns. Developers could write different matching patterns for different proxy rules. - Script injection allowing to add new CSS or Java Script to a website for testing purposes. Detailed instructions and examples of how to use it could be found here: https://www.toni-develops.com/a-homepage-section/projects/using-dev-helper-chrome-extension-for-local-development/