Injecting additional values into an existing env

[af]

Injecting additional values into an existing env

[SimenB]

I think I'd merge the specifications (that is, export SHARED_THING: envalid.str(... instead of passing it to cleanEnv) then do a cleanEnv from your entrypoint.

Thoughts?

[kachkaev]

I had that in mind as well, so that solution would be something like:

// config.ts
import * as envalid from "envalid";

export const sharedValidators = {
  SHARED_THING: envalid.str({
    default: "this variable needs to present in all scripts",
  }),
};

// peculiarTask.ts
import * as envalid from "envalid";
import { sharedValidators } from "./config";

const env = envalid.cleanEnv(process.env, {
  ...sharedValidators,
  EXTRA_THING: envalid.str({
    default: "this variable should only be cleaned inside peculiarTask.ts",
  }),
});

This looks rather clean so far, but has two issues:

1. I have to import envalid from "envalid" in every entrypoint and run const env = envalid.cleanEnv(process.env, sharedValidators, { strict: true }) despite that most of my commands have no peculiar configs.

2. I can't derive stuff from the shared env in my config.ts such as:

// config.ts
import * as envalid from "envalid";
import SharedThingManager from "things";
import * as path from "path";

export const env = envalid.cleanEnv(process.env, {
  SHARED_THING: envalid.str({
    default: "this variable needs to present in all scripts",
  }),
}, { strict: true });

// example 1
export const sharedThingManager = new SharedThingManager(env.SHARED_THING);

// example 2
export const resolvedSharedThing = path.resolve(__dirname, env.SHARED_THING);

[af]

This has been open for a long while and I think the solution of sharing the config (like below) is the best way to go. If there's a more actionable proposal, please open a new issue, going to close this one now

const env = envalid.cleanEnv(process.env, {
  ...sharedValidators,
  EXTRA_THING: envalid.str({
    default: "this variable should only be cleaned inside peculiarTask.ts",
  }),
});