Inspecting an Env

An env may be composed by various flows and their respected configs. It is also possible for one env to support more flows than another.
Get the actual setup for a component by running the env command:

bit env get teambit.base-ui/button
Copied

The result output describes all applied services and their configs.

The tasks set to run as part of the various build processes and their order of execution.

For example:

teambit.pipelines/builder

total 6 tasks are configured to be executed in the following order
1. teambit.harmony/aspect:CoreExporter
2. teambit.compilation/compiler:TSCompiler
3. teambit.defender/tester:TestComponents
4. teambit.pkg/pkg:PreparePackages
5. teambit.pkg/pkg:PublishDryRun
6. teambit.preview/preview:GeneratePreview
Copied

An Env implements various dev services using specific Aspects, with specific configurations. These aspects often use third-party tools like Webpack, TypeScript, etc. The env command gives quick insight into all these tools.

For example, the following output shows TypeScript as the tool used by the Compiler implementation, the version of TypeScript and its (calculated) config (tsconfig.json):

teambit.compilation/compiler

configured compiler: teambit.typescript/typescript (TypeScript @ 4.4.2)
compiler config:
{
  "compilerOptions": {
    "lib": [
      "es2019",
      "DOM",
      "ES6",
      "DOM.Iterable"
    ],
    "target": "es2015",
    "module": "commonjs",
    "jsx": "react",
    "declaration": true,
    "sourceMap": true,
    "skipLibCheck": true,
    "moduleResolution": "node",
    "esModuleInterop": true,
    "outDir": "dist"
  },
  "exclude": [
    "dist"
  ]
}
Copied