PortableGit via npm

🔄 Redistribution of Git for Windows' PortableGit via npm

npx -p portablegit git add --all npx -p portablegit git commit --message "Hello world!" npx -p portablegit bash -c "grep version package.json" npx -p portablegit sh ./build.sh npx -p portablegit git-bash npx -p portablegit gitk HEAD

🔶 Use Git for Windows via npm
👨‍💻 Provides bash via Git Bash
💾 Uses a portable installation of Git & friends
🟦 Only works on Windows x64

Installation

🛑 Only works on Windows x64 systems. Does not work on macOS or Linux.

You can install this package using npm or your favorite npm package manager. If possible you should use the user or global Git for Windows installation instead of this package.

npm install --save-dev portablegit

^{This package has a postinstall script}

⚠️ It's not recommended to install this package globally! Install Git for Windows normally on your system instead. Interested in installing Git globally on more that just Windows machines? Check out Git - Installing Git.

Usage

ℹ There is no JavaScript component to this package; it's just a redistribution of the PortableGit files and binaries.

You can use this package just as you would any other npm package that provides binaries! PortableGit only provides binaries for Windows.

npx -p portablegit git --version
#=> git version 2.X.Y.windows.Z

Available binary commands exposed through this npm package are:

• bash: Git Bash bash.exe. Useful for cross-platform scripting. You can run Bash scripts on Windows!
• sh: Git Bash sh.exe. Runs bash.exe in POSIX mode.
• git: The actual git.exe binary for Windows. See the Git website to learn more about Git.
• git-bash: Launches a terminal emulator running Git Bash. Uses MinTTY.
• git-cmd: Starts a cmd.exe subshell preloaded with git.exe and other things in $PATH. Does not launch a new window.
• git-gui: Starts the Git GUI.
• gitk: Starts the GitK GUI.
• tig, start-ssh-agent, start-ssh-pagent, scalar, git-receive-pack git-upload-pack: Extra things that I'm not not smart enough to understand.

This portablegit npm package is versioned to follow Git for Windows releases. For example, Git for Windows v2.45.1.windows.1 (derived from Git 2.45.1) would be released as portablegit@2.45.11 on npm. Note that there's a 1 suffix appended to the version number. Git for Windows v2.45.1.windows.2 would then be released as portablegit@2.45.12 on npm. The suffix is now a 2 just like .windows.2. For X.Y.0.windows.1 releases the npm-ified X.Y.01 version specifier is invalid; we need to drop the leading zero to create an X.Y.1 release.

You can import.meta.resolve() or require.resolve() anything that would normally be in the extracted PortableGit/* folder. Here's an example:

const cat = import.meta.resolve("portablegit/usr/bin/cat");
console.log(cat);
//=> 'file:///C:/myproject/node_modules/portablegit/out/portablegit/usr/bin/cat'

const cut = require.resolve("portablegit/usr/bin/cut");
console.log(cut);
//=> 'C:\\myproject\\node_modules\\portablegit\\out\\portablegit\\usr\\bin\\cut'

This can be useful if you need to resolve the path to a specific binary (cat.exe, cut.exe, etc.) that isn't exposed by default.

Development

• You'll need a Windows computer to test this package locally.
• You can run npm run build to make sure everything looks good locally.
• npm run generate redownloads the configured version of Git for Windows PortableGit as a 7zip self-extracting archive.
• Each new upcoming release should first be tried as a prerelease X.Y.Z-rc.N.
• This package currently relies on manual updates to bump the Git for Windows version.
• Make sure you update the version field in package.json and the constants in scripts.js generate().
• This project may in the future start squashing Git history or use Git LFS to reduce the repository size.
• npm run build currently has a system dependency on the 7z command. You can install 7zip from 7-zip.org.

Steps to release:

1. Change the version in package.json to the new version RC like 2.45.21-rc.1.
2. Change the version in scripts.js generate() to the new version tag like 2.45.2.windows.1.
3. Change the file name in scripts.js generate() to the new version tag like PortableGit-2.45.2-64-bit.7z.exe.
4. Run npm run generate to vendor the new version.
5. Run npm run build and npm test to make sure everything works. Check that git --version matches the new version.
6. Push to GitHub.
7. Create a new release on GitHub with the new v2.45.21-rc.1 tag.
8. Watch and wait for CI to pass. This will publush a next 2.45.21-rc.1 version to npm.
9. Make sure it works using npx -p portablegit@next git --version or similar.
10. Change the version in package.json to the new version like 2.45.21.
11. Push to GitHub.
12. Create a new release on GitHub with the new v2.45.21 tag.
13. Watch and wait for CI to pass. This will publish a latest 2.45.21 version to npm.

TL;DR: Do a prelease -rc.1 first to make sure things work before doing the actual release. This lets us mirror the Git for Windows version numbers without a special suffix if we get things wrong.