Downloads of v 0.0.1:


Last Update:

01 Mar 2013

Package Maintainer(s):

Software Author(s):

  • Various


Google Chrome Extension Development Web

Chrome - Web Development Extensions

This is not the latest version of Chrome - Web Development Extensions available.

  • 1
  • 2
  • 3

0.0.1 | Updated: 01 Mar 2013



Downloads of v 0.0.1:



Software Author(s):

  • Various

  • 1
  • 2
  • 3
Chrome - Web Development Extensions 0.0.1

This is not the latest version of Chrome - Web Development Extensions available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Chrome - Web Development Extensions, run the following command from the command line or from PowerShell:


To upgrade Chrome - Web Development Extensions, run the following command from the command line or from PowerShell:


To uninstall Chrome - Web Development Extensions, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade ethanbrown.chromedevextensions -y --source="'INTERNAL REPO URL'" --version="'0.0.1'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade ethanbrown.chromedevextensions -y --source="'INTERNAL REPO URL'" --version="'0.0.1'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install ethanbrown.chromedevextensions
    name: ethanbrown.chromedevextensions
    version: '0.0.1'
    state: present

See docs at

chocolatey_package 'ethanbrown.chromedevextensions' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.0.1'

See docs at

cChocoPackageInstaller ethanbrown.chromedevextensions
    Name     = "ethanbrown.chromedevextensions"
    Version  = "0.0.1"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'ethanbrown.chromedevextensions':
  ensure   => '0.0.1',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.


Includes a number of very useful extensions for web application
development within Chrome.

WARNING: This is not a "silent" installer. Assumes installation of the
dev version of Chrome, and not stable or beta.

Chrome no longer provides any ability to automatically install extensions
due to abuse, so the existing preferences file is examined, to determine
what is currently installed.

For plugins that are not installed, Chrome is launched with each extension
in a new browser tab, where the user must press the 'Add To Chrome' button.


- Batarang for AngularJS development

- Clear Cache

- DevTools AutoSave

- PageSpeed Insights

- YSlow

- Simple REST Client

Postman is the preferred client, but requires login, which is
often undesireable with a test browser

- Speed Tracer

- CoffeeConsole

CoffeeScript IDE is preferred, but requires login

Previously Included

- LiveReload
Grunt-contrib-livereload plugin now handles this

- Tincr
Hasn't been updated recently, and Chrome workspaces might supercede this

Under evaluation

- Grunt DevTools

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Chrome - Web Development Extensions 0.0.1 527 Friday, March 1, 2013 Unknown
Discussion for the Chrome - Web Development Extensions Package

Ground Rules:

  • This discussion is only about Chrome - Web Development Extensions and the Chrome - Web Development Extensions package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Chrome - Web Development Extensions, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus