I have a workspace with tracked components, and my compiler is configured in the bit config object, but not imported yet.
Then I run bit build and I expect that bit import the compiler first, and then build the components, but I get errors on data that the compiler not receive.
{
"bit": {
"env": {
"compiler": "bit.envs/compilers/typescript@[version]"
}
}
}
bit buildAdd any other context about the problem here.

Import the compiler bit import COMPILER LINK before running the bit build command.
The disadvantage of this solution: if you have a special configuration in the rawConfig object, they will be removed when you import the compiler.
You can see a solution I wrote to keep the configuration after the import:
https://github.com/teambit/envs/blob/master/.github/workflows/ci.yaml#L45
That works for the second time.
Only if the compiler is installed as part of the build it's not working. looks like a missing reloads for something after importing the compiler.
I am also experiencing this issue, but specifically mine only occurs when running in a circle-ci pipeline and works fine locally.
Any suggested work arounds for this issue?
Any suggested work arounds for this issue?
I have just written a Temporary Solution in the opening comment.
Thanks @JoshK2 the solution above does work in our Circle-CI pipeline now.
This should be solved as part of the next major version - harmony
Most helpful comment
Thanks @JoshK2 the solution above does work in our Circle-CI pipeline now.