Detects if you are accessing localhost or production and respectively shows prominent red banner only on localhost.

Latest Version

Version
0.3
Update
April 25, 2019
Size
37.79KiB
Developer
Category
Users
266
Rating
4 ★
Manifest Version
2
Web Store Status
Languages Support
English
See more
Permissions
See more

Localhost detector Extension

It checks the following in the URL and adds the red banner:
1. \"localhost\"
2. \"127.0.0.1\"
3. \"local.\"
4. \".local\"
5. \"staging.\"
6. \".stg\"
7. \"dev.\"
8. \"test.\"
9. \".test\"


Let me know, if you want to add any other string that should match and show the red banner.
Read more

Source Manifest.json

{"update_url": "https://clients2.google.com/service/update2/crx", "manifest_version": 2, "name": "Localhost detector", "description": "Detects if you are accessing localhost or production and respectively shows prominent red banner only on localhost.", "version": "0.3", "icons": { "128": "icon.png" }, "content_scripts": [ { "js": ["jquery.min.js", "local.js"], "css": ["local.css"], "matches": [ "*://*/*" ], "run_at": "document_end" } ]}
Read more

How to download and manually install Localhost detector extension for Chrome

Looking for a way to install Localhost detector extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.

However, you may need to install Localhost detector extensions manually, this article outlines two simple methods to effortlessly install Localhost detector extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.

Method 1: Download Localhost detector extension and manually install through Drag &Drop

If you ever need to manually install a Localhost detector extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.

Step 1: Download the Localhost detector Extension by clicking the "Download CRX" button on the website.

Look for the Localhost detector extension you wish to install. Go to the website and download the Localhost detector extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for Localhost detector extension that contains all the data.

Step 2: Extract &Arrange Files

Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.

Step 3: Go to the Chrome Extensions Page

Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.

Step 4: Drag and Drop the Extension

Now, go to the folder where you extracted the Localhost detector extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.

Step 5: Complete the Installation

Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.

Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.

Method 2: Download Localhost detector extension for Chrome and install in Developer Mode

This is another method to install Localhost detector extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.

Step 1: Download the Localhost detector extension file

Select and download the Localhost detector extension by clicking the 'Download CRX' button on the website.

Step 2: Extract the downloaded contents

Convert the file to a ZIP file if it is in CRX format then extract the Localhost detector extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your Localhost detector extension running.

Step 3: Open Chrome Extension Setting Page

In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.

Step 4: Enable Developer Mode

After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.

Step 5: Load the Unpacked Extension

Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."

Step 6: Select the Extension Folder

Once the pop-up opens upon clicking Load unpacked, select the Localhost detector extension directory and click on the "Select Folder "button.

Step 7: Confirm and Install

After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.

Conclusion

Here we've made a step-by-step guide on How to manually install Localhost detector extension in 2 ways. We hope this guide proves helpful.

Similar Extensions

icon

Am I working on localhost? Extension · Developer Tools 266 0 ★ 38.95KiB

icon

Localhost Automate Extension · Developer Tools 266 12 ★ 85.98KiB

icon

Server Status Extension · Developer Tools 266 10 ★ 341KiB

icon

IP & Downlink Utility Extension · Productivity 266 0 ★ 245KiB

icon

Switch environment Extension · Developer Tools 266 4 ★ 43.0KiB

icon

Link Router Extension · Productivity 266 4 ★ 29.05KiB

icon

LL Developer Tools Extension · Developer Tools 266 1 ★ 98.88KiB

icon

localhost Extension · Developer Tools 266 0 ★ 21.1KiB

icon

Lavaca Developer Tools Extension · Developer Tools 266 0 ★ 10.42MiB

icon

Input hidden Monitor Extension · Developer Tools 266 0 ★ 36.05KiB

icon

LocoHost Extension · Developer Tools 266 3 ★ 117KiB

icon

C-Strip Extension · Developer Tools 266 2 ★ 8.62KiB

icon

Scripter debugger extension Extension · Developer Tools 266 2 ★ 1.04MiB

icon

Libraries.io | GitHub Companion Extension · Productivity 266 3 ★ 1.31MiB

icon

Admin tools Extension · Developer Tools 266 1 ★ 62.79KiB

icon

DOM-JSON Tree Matcher Extension · Developer Tools 266 0 ★ 18.58KiB

icon

Not my department Extension · Developer Tools 266 1 ★ 1.44MiB

icon

LiveScriptConsole Extension · Developer Tools 266 2 ★ 388KiB

icon

DOM to JSON Selector Extension · Developer Tools 266 0 ★ 48.55KiB

icon

HTML5 Debugger Extension · Developer Tools 266 1 ★ 9.01KiB

icon

Developer search tool Extension · Productivity 266 4 ★ 123KiB

icon

Dev Playground Extension · Developer Tools 266 2 ★ 288KiB

icon

Policy Control Extension · Productivity 266 3 ★ 48.47KiB

icon

Developer pages Extension · Developer Tools 266 5 ★ 7.09KiB

User reviews

icon

Sheldon Hull (ID: 0000003407da72fc) Voted 3 ★ - Updated 05/22/2023 I like the idea. Unfortunately, there are sites that have dev in them that this triggers on, like `dev.azure.com` for example. This means I have the banner popup in places it shouldn't be. Without any ability to customize the matching I had to uninstall. It's a cool idea though!

icon

Lec “Lecpo” Pol (ID: 0000001d4f3de190) Voted 5 ★ - Updated 04/12/2019 Simple and useful.

icon

Herbert Smith (ID: 0000006ebdc9c030) Voted 5 ★ - Updated 02/04/2019 Extensão TOP, procurei bastante e não encontrei, quando achei aqui não acreditei de primeira, mas funciona perfeitamente para localhost com ou sem porta! Parabéns ao criador.

icon

Ovidijus Sobutas (ID: 00000065df7428c2) Voted 2 ★ - Updated 03/15/2018 Works only by reading url, so no way to know if you're on localhost when using virtual hosts.

icon

Patrick Man (ID: 000000d1e26838dd) Voted 5 ★ - Updated 01/24/2018 Love this one! So nice to have a big bright visual cue to distinguish local experimental development from breaking things on the live server *grin*