Skip to content
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

Bit Install - @babel/runtime/helpers #7898

Closed
pm-trey opened this issue Sep 12, 2023 · 2 comments
Closed

Bit Install - @babel/runtime/helpers #7898

pm-trey opened this issue Sep 12, 2023 · 2 comments
Labels

Comments

@pm-trey
Copy link

pm-trey commented Sep 12, 2023

Describe the bug

bit commands will not succeed, neither in stable nor nightly builds. Have tried a number of resolutions, but continue to receive the error.

Steps to Reproduce

  1. bit install
  2. bit status

Expected Behavior

Commands succeed

Screenshots, exceptions and logs

➜  PM-onboarding-react-app git:(develop) bit install
  Resolving component dependencies for workspace: 'my-workspace-name'
✔ importing components (completed in 1s)
  installing dependencies in workspace using yarn (teambit.dependencies/yarn)
Bit received an error loading teambit.node/[email protected], due to the error:
"Cannot find module '@babel/runtime/helpers/interopRequireDefault'".
This is required for the component: unknown
Please use the '--log=error' flag for the full error.
try running "bit install" to fix this issue

Specifications

  • Bit version: 0.2.40 & Nightly
  • Workspace type: harmony
  • Node version: 18.17.1
  • npm / yarn version: 3.6.1
  • Platform: macOS
@pm-trey pm-trey changed the title Bit Install - @babel/runtime/helpers not Bit Install - @babel/runtime/helpers Sep 12, 2023
@pm-trey
Copy link
Author

pm-trey commented Sep 12, 2023

Resolved by changing env from teambit.node/[email protected] to teambit.harmony/node

@pm-trey pm-trey closed this as completed Sep 12, 2023
@GiladShoham
Copy link
Member

This is not a great solution.
This caused usually by corrupted capsule.
So bit capsule delete --all
Usually solves this issue without moving to the old node env

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants