Skip to content

Conversation

@zkochan
Copy link
Member

@zkochan zkochan commented Sep 2, 2025

Proposed Changes

  • This field prevents accidental runs of npm install on the repository. npm install from v11 will fails with this error:
    npm error code EBADDEVENGINES
    npm error EBADDEVENGINES The developer of this package has specified the following through devEngines
    npm error EBADDEVENGINES Invalid engine "packageManager"
    npm error EBADDEVENGINES Invalid name "bit" does not match "npm" for "packageManager"
    npm error EBADDEVENGINES {
    npm error EBADDEVENGINES   current: { name: 'npm', version: '11.5.2' },
    npm error EBADDEVENGINES   required: { name: 'bit' }
    npm error EBADDEVENGINES }
    

@zkochan
Copy link
Member Author

zkochan commented Sep 2, 2025

So, we actually can't really use it because we use npm run in CI... Could we possibly use bit for the scripting?

@GiladShoham
Copy link
Member

yes, @davidfirst just implemented that feature few days ago.
see #10028

@davidfirst
Copy link
Member

@GiladShoham for some scripts, like npm run full-setup, it won’t work because the bit script command requires the env to be ready in order to fetch the scripts. But right after cloning the repo, the env isn’t available yet — it actually depends on npm run full-setup to initialize. So it ends up being a bit of a chicken-and-egg situation.

@GiladShoham
Copy link
Member

Ok i understand
In that case i don't think it worth the effort.
It's not that we have tons of developers trying to run npm install on bit repo..

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