Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...

Downloads:
117,936
Downloads of v 0.2.2.20180420:
3,370
Last Update:
21 Apr 2018
Package Maintainer(s):
Software Author(s):
- Neovim contributors
Tags:
vi vim gvim neovim text editor sublime atom emacs notepad
Neovim
This is not the latest version of Neovim available.
Downloads:
117,936
Downloads of v 0.2.2.20180420:
3,370
Software Author(s):
- Neovim contributors
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
Neovim 0.2.2.20180420
This is not the latest version of Neovim available.
All Checks are Passing
2 Passing Test
To install Neovim, run the following command from the command line or from PowerShell:
To upgrade Neovim, run the following command from the command line or from PowerShell:
To uninstall Neovim, run the following command from the command line or from PowerShell:
NOTE: This applies to both open source and commercial editions of Chocolatey.
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 https://chocolatey.org/api/v2. 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
-
Open Source
- Download the Package Download
- Follow manual internalization instructions
-
Package Internalizer (C4B)
- Run
choco download neovim --internalize --version=0.2.2.20180420 --source=https://chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade neovim -y --source="'STEP 3 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 neovim -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Ensure neovim installed
win_chocolatey:
name: neovim
state: present
version: 0.2.2.20180420
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
Coming early 2020! Central Managment Reporting available now! More information...
chocolatey_package 'neovim' do
action :install
version '0.2.2.20180420'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: neovim,
Version: 0.2.2.20180420,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller neovim
{
Name = 'neovim'
Ensure = 'Present'
Version = '0.2.2.20180420'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'neovim':
provider => 'chocolatey',
ensure => '0.2.2.20180420',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install neovim version="0.2.2.20180420" source="STEP 3 URL"
See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.
5. 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 27 May 2018.
More powerful plugins
- The msgpack API enables structured communication to and from any programming language.
- Remote plugins run as co-processes that communicate with Neovim safely and asynchronously.
Better out-of-the-box
- Strong defaults
- Modern terminal features such as truecolor and bracketed paste
- Built-in terminal emulator
- First-class embedding
- GUIs (or TUIs—such as readline) can nvim --embed or communicate via TCP socket using the discoverable msgpack API.
Drop-in replacement for Vim
- Neovim is an extension of Vim: feature-parity and backwards compatibility are high priorities.
- If you are already familiar with Vim, see :help nvim-from-vim to learn about the differences.
# File: chocolateybeforemodify.ps1
# Description: Updating neovim
# Author: Reinaldo Molina
# Email: rmolin88 at gmail dot com
# Revision: 0.0.0
# Last Modified: Fri Apr 20 2018 22:49
#
$packageName = "neovim"
$destDir = Join-Path $(Get-ToolsLocation) $packageName
Remove-Item $destDir -Force -Recurse
# Exit with the result of the last command
exit $?
# File: chocolateyinstall.ps1
# Description: Installation of Neovim
# Author: Reinaldo Molina
# Email: rmolin88 at gmail dot com
# Revision: 0.0.0
# Last Modified: Fri Apr 20 2018 23:04
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageName= 'neovim' # arbitrary name for the package, used in messages
$destDir = Join-Path $(Get-ToolsLocation) $packageName
$url = 'https://github.com/neovim/neovim/releases/download/v0.2.2/nvim-win32.zip' # download url, HTTPS preferred
$url64 = 'https://github.com/neovim/neovim/releases/download/v0.2.2/nvim-win64.zip' # 64bit URL here (HTTPS preferred) or remove - if installer contains both (very rare), use $url
$bin = $destDir + '\Neovim\bin'
$packageArgs = @{
packageName = $packageName
unzipLocation = $destDir
url = $url
url64bit = $url64
softwareName = 'neovim*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
checksum = 'EDBB17047F9A1BDC01ACF965430EBBC61BD05A9D39668C9CC6961EA47F471C47'
checksumType = 'sha256' #default is md5, can also be sha1, sha256 or sha512
checksum64 = '66BAB53EC0A8AFF854921B6925630026649F3A49BB7913D19A4A602FFC138C92'
checksumType64= 'sha256' #default is checksumType
validExitCodes= @(0) #please insert other valid exit codes here
}
# https://chocolatey.org/docs/helpers-install-chocolatey-package
Install-ChocolateyZipPackage @packageArgs
# Adds neovim to the path if not present already
Install-ChocolateyPath -PathToInstall $bin
Write-Output "Please Consider donating https://salt.bountysource.com/teams/neovim"
Write-Output "Issues? Please visit https://github.com/neovim/neovim/wiki/Installing-Neovim"
# File: chocolateyuninstall.ps1
# Description: Uninstallation of neovim
# Author: Reinaldo Molina
# Email: rmolin88 at gmail dot com
# Revision: 0.0.0
# Last Modified: Fri Apr 20 2018 22:50
#
$packageName= 'neovim' # arbitrary name for the package, used in messages
$destDir = Join-Path $(Get-ToolsLocation) $packageName
$bin = $destDir + '\Neovim\bin'
Write-Output "Please manually remove `"$($bin)`" from the User PATH environment variable if not installing neovim again."
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.
Version | Downloads | Last Updated | Status |
---|---|---|---|
Neovim 0.5.0-beta | 5614 | Friday, April 3, 2020 | Approved |
Neovim 0.4.5.20210116-beta | 4 | Monday, January 18, 2021 | Approved |
Neovim 0.4.5-beta | 31 | Thursday, August 13, 2020 | Exempted |
Neovim 0.4.4.20210116 | 1442 | Monday, January 18, 2021 | Approved |
Neovim 0.4.4 | 19895 | Wednesday, September 9, 2020 | Approved |
Neovim 0.4.3 | 26284 | Monday, November 18, 2019 | Approved |
Neovim 0.4.2 | 5248 | Monday, September 16, 2019 | Approved |
Neovim 0.3.8 | 5401 | Friday, July 5, 2019 | Approved |
Neovim 0.3.7 | 2070 | Friday, June 14, 2019 | Approved |
Neovim 0.3.6 | 1189 | Wednesday, June 5, 2019 | Approved |
Neovim 0.3.5 | 3518 | Tuesday, April 30, 2019 | Approved |
Neovim 0.3.4 | 5683 | Friday, February 1, 2019 | Approved |
Neovim 0.3.3 | 1393 | Friday, January 18, 2019 | Approved |
Neovim 0.3.2.88-beta | 598 | Friday, July 20, 2018 | Approved |
Neovim 0.3.2 | 1155 | Saturday, January 5, 2019 | Approved |
Neovim 0.3.1 | 7493 | Friday, July 20, 2018 | Approved |
Neovim 0.3.0 | 2246 | Thursday, June 14, 2018 | Approved |
Neovim 0.3.0-beta | 147 | Thursday, June 14, 2018 | Approved |
Neovim 0.2.2.20180420 | 3370 | Saturday, April 21, 2018 | Approved |
Neovim 0.2.2.20180416 | 703 | Monday, April 16, 2018 | Approved |
Neovim 0.2.2.988-beta | 220 | Saturday, April 21, 2018 | Approved |
Neovim 0.2.2.900-beta | 248 | Monday, April 9, 2018 | Approved |
Neovim 0.2.2 | 7296 | Thursday, November 30, 2017 | Approved |
Neovim 0.2.1.329-beta | 1315 | Saturday, June 10, 2017 | Exempted |
Neovim 0.2.1.258-beta | 388 | Monday, May 29, 2017 | Exempted |
Neovim 0.2.1.244-beta | 284 | Wednesday, May 24, 2017 | Exempted |
Neovim 0.2.1 | 2335 | Saturday, November 11, 2017 | Approved |
Neovim 0.2.0.20170610 | 7821 | Saturday, June 10, 2017 | Approved |
Neovim 0.2.0 | 1655 | Wednesday, May 24, 2017 | Approved |
Neovim - experimental 0.0.0.928-nightly | 487 | Friday, June 10, 2016 | Exempted |
Neovim - experimental 0.0.0.926-nightly | 328 | Thursday, June 2, 2016 | Exempted |
Neovim - experimental 0.0.0.924-nightly | 352 | Tuesday, May 31, 2016 | Exempted |
Neovim - experimental 0.0.0.866-nightly | 286 | Thursday, May 26, 2016 | Exempted |
Neovim - experimental 0.0.0.856-nightly | 292 | Wednesday, May 25, 2016 | Exempted |
Neovim - nightly build 0.0.0.836-nightly | 325 | Saturday, May 14, 2016 | Exempted |
Copyright Neovim contributors. All rights reserved.
Ground Rules:
- This discussion is only about Neovim and the Neovim 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 Neovim, 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.