-
Notifications
You must be signed in to change notification settings - Fork 920
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
Multiple issues when trying to tag many components #8868
Labels
Comments
Can you please run just |
I'm closing as this the main error was a component that was not assigned the correct environment. When I then did a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm working on a project I've had going for a while with a lot of components. I hadn't previously been using the bit tag workflow and instead just using git. This was fine for me as I'm trying to transition an old project into using Bit but now I need to use the build pipeline I can't do this without tagging/snapping.
I'm hitting a few issues when trying to start tagging my components. To try and reduce issues I started by tagging the components with little or no dependencies. This seemed to work fine. As an example I have a
core/lib
package that just contains type definitions in.ts
files.I can then snap components that are dependent on the
core/lib
package but when I runbit build
I start to get a few errors. Withbit build
I get the following error:✖ env: cam-org.cam/envs/react-env-custom@706551995ad73fb60691ec028994b62d62f812e5, task "teambit.compilation/compiler:TypescriptCompile" threw an error Debug Failure.
If I try
bit build <component-pattern>
where<component-pattern>
doesn't includes thecore/lib
package I get the following error:If I try
bit build <component-pattern>
where<component-pattern>
includes thecore/lib
package I get the following error:Expected Behavior
Should build the components.
Specifications
1.6.145
v18.19.1
v10.2.1
ubuntu
Envs:
The text was updated successfully, but these errors were encountered: