v5.0.0

Changelog

[5.0.0] - 2024-08-09

Breaking Changes

• Output directory structure changed: Full repository downloads now create a subfolder matching the repository name (like git clone)
• File paths changed: Users need to account for the new subfolder level in their output directory

What this means in practice:

Before (v4.x):

# Running from ~/mydevspace/
goGitIt('https://github.com/extension-js/extension.js')
# Result: Files went directly into ~/mydevspace/
~/mydevspace/
├── README.md
├── package.json
├── src/
└── templates/

After (v5.0.0):

# Running from ~/mydevspace/
goGitIt('https://github.com/extension-js/extension.js')
# Result: Files go into ~/mydevspace/extension.js/ (creates subfolder!)
~/mydevspace/
└── extension.js/          # ← NEW subfolder created
    ├── README.md
    ├── package.json
    ├── src/
    └── templates/

Important Note: The second argument (output directory) only controls WHERE the content goes, not WHAT it's called. For subfolder/file downloads, the original folder/file name is preserved.

Bug Fixes

• Fixed temporary directory conflicts that could cause download failures
• Improved cleanup of temporary files on all platforms

Migration

For end users: Update your code to account for the new subfolder structure. Full repository downloads now create an additional subfolder level.

Examples of what changed:

# v4.x behavior
goGitIt('https://github.com/user/repo')
# Files went to: ./README.md, ./package.json, etc.

# v5.0.0 behavior  
goGitIt('https://github.com/user/repo')
# Files go to: ./repo/README.md, ./repo/package.json, etc.

---

v4.0.0...v5.0.0

Full Changelog: v4.0.0...v5.0.0