How can development and production modes be separated?

Issue type:

[ O ] question [ ] bug report [ ] feature request [ ] documentation issue

TypeORM version:

[ O ] latest [ ] @next [ ] 0.x.x (or put your version here)

I want to divide the development and deployment mode into .env files or ormconfig.json.

[kieuminhcanh]

I recommended use ormconfig.js to setting.

ormconfig.js

const rootDir = process.env.NODE_ENV === "development" ?
  "src" :
  "build/src"

module.exports = {
  ...
  "entities": [rootDir + "/entities/**/*.{js,ts}"],
  "migrations": [rootDir + "/migrations/*.{js,ts}"],
  "subscribers": [rootDir + "/subscribers/**/*.{js,ts}"],
  "seeds": [rootDir + "/migrations/seeds/**/*.{js,ts}"],
  "factories": [rootDir + "/migrations/factories/**/*.{js,ts}"],
  ...
}

tsconfig.json

{
  "compilerOptions": {
    ...
    "outDir": "./build",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "sourceMap": true,
    ...
  },
  ...
}

And then, update your scripts in package.json package.json

"scripts": {
    "start": "set debug=* && ts-node-dev --respawn --transpileOnly ./src/index.ts",
    "prod": "tsc && node ./build/src/index.js",    <== Focus to this line
  }

[Kononnable]

@havenchyk I’m not sure if this should be added to documentation, maybe as an example. This can be achieved many different ways and it’s not completely typeorm problem.

But to be honest I don’t like an idea of ormconfig file at all. It is good for CLI but I think libraries shouldn’t have specific configurations files - configuration should be provided by the application which uses library and should be kept with other app configuration options.