Downloads of v 0.10.9:


Last Update:

19 Oct 2017

Package Maintainer(s):

Software Author(s):

  • Bit Maintainers


bit node nodejs npm javascript packages bower admin

Bit (Install)

  • 1
  • 2
  • 3

0.10.9 | Updated: 19 Oct 2017



Downloads of v 0.10.9:



Software Author(s):

  • Bit Maintainers

  • 1
  • 2
  • 3
Bit (Install) 0.10.9

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


Deployment Method: Individual Install, Upgrade, & Uninstall

To install Bit (Install), run the following command from the command line or from PowerShell:


To upgrade Bit (Install), run the following command from the command line or from PowerShell:


To uninstall Bit (Install), 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 bit -y --source="'INTERNAL REPO URL'" [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 bit -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install bit
    name: bit
    version: '0.10.9'
    state: present

See docs at

chocolatey_package 'bit' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.10.9'

See docs at

cChocoPackageInstaller bit
    Name     = "bit"
    Version  = "0.10.9"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'bit':
  ensure   => '0.10.9',
  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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 10 Jul 2020.


Bit is a distributed code component manager.

Increase reusability: Designed for fast and easy extraction and reuse of code
components without creating duplications or publishing packages..

Simply and predictable: Bit uses features such as simple inline editing,
strict minor versioning and test based updating to make modifying and maintaining
is super simple.

Discoverable: Bit uses a functionality-based search and a simple yet smart
scoping mechanism to easily find and reuse components created by you or by others.

$ErrorActionPreference = 'Stop'; # stop on all errors
$packageName = 'bit'
$packageArgs = @{
  packageName = $packageName
  softwareName = 'Bit*'
  fileType = 'msi'
  silentArgs = "/qn /norestart /l*v `"$env:TEMP\chocolatey\$($packageName)\$($packageName).MsiInstall.log`""
  validExitCodes = @(0, 3010, 1641)
  checksumType = 'sha256'

  url = ''
  checksum = 'B13016C77E11123BEC8019620E3AD937AB69F08F613D29A48E690A3CCDDA67A0'

Install-ChocolateyPackage @packageArgs

# Update Bit package.json file so it can tell that it was installed via Chocolatey.
if (Test-Path "${env:ProgramFiles(x86)}\Bit\package.json") {
  $path = "${env:ProgramFiles(x86)}\Bit\package.json"
} else {
  $path = "$env:ProgramFiles\Bit\package.json"
$script = @"
  (Get-Content -Path '$path') ``
    -replace 'installationMethod":.+', 'installationMethod": "choco"' ``
    | Set-Content '$path'
Start-ChocolateyProcessAsAdmin -Statements $script

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
Bit (Install) 0.10.7 372 Thursday, September 7, 2017 Approved
Bit (Install) 0.6.4 361 Sunday, June 25, 2017 Approved
Bit (Install) 0.6.0 339 Tuesday, May 16, 2017 Approved
Bit (Install) 0.5.3 337 Monday, May 1, 2017 Approved
Bit (Install) 0.5.0 334 Tuesday, April 4, 2017 Approved
Bit (Install) 0.1.15 363 Wednesday, February 1, 2017 Approved

This package has no dependencies.

Discussion for the Bit (Install) Package

Ground Rules:

  • This discussion is only about Bit (Install) and the Bit (Install) 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 Bit (Install), 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