Allow to configure --env-mode=loose in turbo.json

[NatoBoram]

Goals

Not clear why this is not already an option, as the desired effect is to have consistent behavior across all envs.

Non-goals

Make it harder to transition from Turbo 1 to Turbo 2 in large monorepos by not having this option

Background

• Allow to configure --env-mode strict in turbo.json #6481

Proposal

Adding envMode setting to turbo.json

[Hacksore]

I just upgraded from turbo v1 to v2 and found that it broke my workflow with 1password. Seems very unfortunate that I have to pass --env-mode loose explicitly to turbo commands instead of a global config setting in turbo.json.

I very much support this proposed ask ❤️.

https://github.com/Hacksore/1password-cli-env

[Snailedlt]

You can just add this to your turbo.json, to give every task access to every env variable. Which afaik is the same thing that --env-mode=loose does:

    "globalEnv": [
        "*"
    ],

[Hacksore]

I just realized an option you have available today is adding env vars to globalEnv.

Hacksore/1password-cli-env@bb12583

cc @anthonyshew

[anthonyshew]

This is being worked on in #8757. Sorry for not seeing this earlier!

[Snailedlt]

Yup, so now that it's merged you can do this:

    "globalEnv": [
        "*"
    ],

[anthonyshew]

We don't recommend this. This would make you miss cache for every task whenever any environment variable changes.

There's a small chance this is your intent, but not likely.

[anthonyshew]

This has shipped! #8757