With custom server, no more remix dev

[jacargentina]

Very nice to have the new server remix.config.js, but not I loose the "hot reload" from remix dev

My current solution is this:

remix.config.dev.js

/**
 * @type {import('@remix-run/dev/config').AppConfig}
 */
module.exports = {
  appDirectory: 'app',
  devServerPort: 8002,
};

remix.config.prod.js

/**
 * @type {import('@remix-run/dev/config').AppConfig}
 */
module.exports = {
  appDirectory: 'app',
  assetsBuildDirectory: 'public/build',
  devServerPort: 8002,
  publicPath: '/build/',
  serverBuildPath: './server.js',
  serverBuildTarget: 'node-cjs',
  server: './server.ts',
};

  "scripts": {
    "dev": "cp remix.config.dev.js remix.config.js; remix dev",
    "server": "cp remix.config.prod.js remix.config.js; npm run build; NODE_ENV=production node server.js",
  },

Some way to avoid copying .config files would be much better!

BTW:this way I must add remix.config.js to .gitignore

[kasperisager]

What I'm currently doing is toggling the config based on process.env.NODE_ENV:

module.exports = process.env.NODE_ENV === "production"
  ? { /* production config, incl. `server` key */ }
  : { /* development config */ }