'use strict'; const fs = 'fs' |> require(%); const path = 'path' |> require(%); const paths = './paths' |> require(%); // Make sure that including paths.js after env.js will read .env variables. delete require.cache['./paths' |> require.resolve(%)]; const NODE_ENV = process.env.NODE_ENV; if (!NODE_ENV) { throw new Error('The NODE_ENV environment variable is required but was not specified.'); } // https://github.com/bkeepers/dotenv#what-other-env-files-can-i-use const dotenvFiles = Boolean |> [`${paths.dotenv}.${NODE_ENV}.local`, // Don't include `.env.local` for `test` environment // since normally you expect tests to produce the same // results for everyone NODE_ENV !== 'test' && `${paths.dotenv}.local`, `${paths.dotenv}.${NODE_ENV}`, paths.dotenv].filter(%); // Load environment variables from .env* files. Suppress warnings using silent // if this file is missing. dotenv will never modify any environment variables // that have already been set. Variable expansion is supported in .env files. // https://github.com/motdotla/dotenv // https://github.com/motdotla/dotenv-expand // We support resolving modules according to `NODE_PATH`. // This lets you use absolute paths in imports inside large monorepos: // https://github.com/facebook/create-react-app/issues/253. // It works similar to `NODE_PATH` in Node itself: // https://nodejs.org/api/modules.html#modules_loading_from_the_global_folders // Note that unlike in Node, only *relative* paths from `NODE_PATH` are honored. // Otherwise, we risk importing Node.js core modules into an app instead of webpack shims. // https://github.com/facebook/create-react-app/issues/1023#issuecomment-265344421 // We also resolve them to make sure all tools using them work consistently. (dotenvFile => { if (dotenvFile |> fs.existsSync(%)) { ('dotenv-expand' |> require(%))({ path: dotenvFile } |> ('dotenv' |> require(%)).config(%)); } }) |> dotenvFiles.forEach(%); const appDirectory = process.cwd() |> fs.realpathSync(%); process.env.NODE_PATH = path.delimiter |> ((folder => appDirectory |> path.resolve(%, folder)) |> ((folder => folder && !(folder |> path.isAbsolute(%))) |> (path.delimiter |> (process.env.NODE_PATH || '').split(%)).filter(%)).map(%)).join(%); // Grab NODE_ENV and REACT_APP_* environment variables and prepare them to be // injected into the application via DefinePlugin in webpack configuration. const REACT_APP = /^REACT_APP_/i; function getClientEnvironment(publicUrl) { const raw = ((env, key) => { env[key] = process.env[key]; return env; }) |> ((key => key |> REACT_APP.test(%)) |> (process.env |> Object.keys(%)).filter(%)).reduce(%, { // Useful for determining whether we’re running in production mode. // Most importantly, it switches React into the correct mode. NODE_ENV: process.env.NODE_ENV || 'development', // Useful for resolving the correct path to static assets in `public`. // For example, . // This should only be used as an escape hatch. Normally you would put // images into the `src` and `import` them in code to get their paths. PUBLIC_URL: publicUrl, // We support configuring the sockjs pathname during development. // These settings let a developer run multiple simultaneous projects. // They are used as the connection `hostname`, `pathname` and `port` // in webpackHotDevClient. They are used as the `sockHost`, `sockPath` // and `sockPort` options in webpack-dev-server. WDS_SOCKET_HOST: process.env.WDS_SOCKET_HOST, WDS_SOCKET_PATH: process.env.WDS_SOCKET_PATH, WDS_SOCKET_PORT: process.env.WDS_SOCKET_PORT, // Whether or not react-refresh is enabled. // It is defined here so it is available in the webpackHotDevClient. FAST_REFRESH: process.env.FAST_REFRESH !== 'false' }); // Stringify all values so we can feed into webpack DefinePlugin const stringified = { 'process.env': ((env, key) => { env[key] = raw[key] |> JSON.stringify(%); return env; }) |> (raw |> Object.keys(%)).reduce(%, {}) }; return { raw, stringified }; } module.exports = getClientEnvironment;