Skip to content

feat(runner): add child process support for specific codemod execution #1489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 18, 2025

Conversation

mohebifar
Copy link
Member

📚 Description

These changes allow for running certain codemods as child node processes with the ability to resolve node modules both from the codemod cli node_modules and cwd. This is just a hack to unblock nodejs codemods.

🔗 Linked Issue

🧪 Test Plan

📄 Documentation to Update

Copy link

vercel bot commented Feb 18, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
codemod ⬜️ Ignored (Inspect) Visit Preview Feb 18, 2025 6:12pm

Copy link

pkg-pr-new bot commented Feb 18, 2025

Open in Stackblitz

npm i https://pkg.pr.new/codemod@1489

commit: b4ca4e0

@mohebifar mohebifar force-pushed the fix/running-node-codemods branch from b0b9536 to d5d1bd9 Compare February 18, 2025 09:41
@mohebifar mohebifar force-pushed the fix/running-node-codemods branch from d5d1bd9 to b4ca4e0 Compare February 18, 2025 18:12
@codemod-com-bot codemod-com-bot merged commit 4b59d50 into main Feb 18, 2025
12 checks passed
@codemod-com-bot codemod-com-bot deleted the fix/running-node-codemods branch February 18, 2025 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants