feat: migrate from nodeenv to bunenv for Bun environment management#136
Merged
JacobCoffee merged 1 commit intomainfrom Nov 24, 2025
Merged
feat: migrate from nodeenv to bunenv for Bun environment management#136JacobCoffee merged 1 commit intomainfrom
JacobCoffee merged 1 commit intomainfrom
Conversation
Replace nodeenv with bunenv for frontend tooling isolation: **Changes:** - Makefile: Replace `nodeenv --python-virtualenv` with `bunenv --python-virtualenv --bun=latest` - pyproject.toml: Add `bunenv>=0.1.0` to dev dependencies - uv.lock: Update lock file with bunenv dependency **Benefits:** ✅ Purpose-built for Bun (vs Node.js-focused nodeenv) ✅ Maintained actively with modern tooling ✅ GitHub Releases API integration (vs nodejs.org index) ✅ Same proven architecture as nodeenv ✅ Zero breaking changes to workflow **Testing:** Verified bunenv 0.1.0 installs correctly via `uv sync --group dev` **Migration Path:** `nodeenv --python-virtualenv` → `bunenv --python-virtualenv --bun=latest` No other changes required - bunenv provides the same isolation and activation mechanism, just optimized for Bun. Related: JacobCoffee/bunenv#7 (bunenv GitHub Action) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Sorry @JacobCoffee, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
|
🚅 Environment byte-pr-136 in byte has no services deployed. |
|
Documentation preview will be available shortly at https://jacobcoffee.github.io/byte-docs-preview/136 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Migrate from
nodeenvtobunenvfor managing Bun environments in the frontend tooling workflow.Motivation
bunenv is purpose-built for Bun (vs nodeenv being Node.js-focused) and provides:
Changes
Modified Files
Makefilepyproject.tomlbunenv>=0.1.0to dev dependenciesuv.lockBenefits
✅ Purpose-Built - Designed specifically for Bun, not adapted from Node.js
✅ Modern API - Uses GitHub Releases API vs legacy nodejs.org index
✅ Active Development - Maintained with latest tooling (uv, ruff, ty)
✅ Zero Breaking Changes - Drop-in replacement for nodeenv
✅ Same Architecture - Based on nodeenv's proven design
Testing
uv sync --group devuv run bunenv --version→0.1.0Migration
The migration is seamless:
Before:
After:
Both create isolated Bun environments within Python virtualenvs. The activation and deactivation mechanisms are identical.
Validation
Please verify CI passes, particularly:
validatejob (linting, type-checking)testjob (pytest)build-docsjob (if it uses frontend tooling)Related
This PR serves as validation before bunenv 1.0 release.
🤖 Generated with Claude Code