Remix v1->v2 - poor build performance on dev with v1-route-convention enabled.

[aaronduce]

After moving from v1 to v2 a few months ago on our primary application - monolith probably pushing 600-700+ routes.

Dev first builds now take

# run 1
 info  building...
 info  built (9.7s)
# run 2
 info  building...
 info  built (13.2s)
# run 3
 info  building...
 info  built (9.4s)

and changes saved builds looking no better:

 info  rebuilding... (~ app/routes/######)
 info  rebuilt (2.6s)
 info  app server ready (138ms)
 info  hmr

 info  rebuilding... (~ app/routes/#####)
 info  rebuilt (2.9s)
 info  app server ready (94ms)
 info  hmr

Sometimes, the remix-serve will hang after the rebuild completes and not start for 5-10 seconds.

Using @remix-run/v1-route-convention and remix.config.js declared as:

/**
 * @type {import('@remix-run/dev').AppConfig}
 */

const {
  createRoutesFromFolders,
} = require("@remix-run/v1-route-convention");

module.exports = {
  ignoredRouteFiles: [".*"],
  serverDependenciesToBundle: ["axios", "public-ip", "got", "p-cancelable", "pdf-merger-js", "@szmarczak/http-timer", "lowercase-keys", "pdfmake", "recharts", "d3-shape", "d3-scale", "d3-array", "d3-time", "d3-interpolate", "d3-format", "d3-time-format", "d3-path", "d3-color", "internmap"],
  
  // appDirectory: "app",
  // assetsBuildDirectory: "public/build",
  // serverBuildPath: "build/index.js",
  // publicPath: "/build/",
  // devServerPort: 8002,

  routes(defineRoutes) {
    // uses the v1 convention, works in v1.15+ and v2
    return createRoutesFromFolders(defineRoutes);
  },
  browserNodeBuiltinsPolyfill: { modules: { crypto: true } },
  serverModuleFormat: "cjs",
  tailwind: true,
};

I have many other projects, personal and work, set up this exact way, tailwind, cjs, v1 route convention, and none of them behave like this one. All the rest are near instant rebuilds, and 3-4 second first builds, on v2.

Any ideas?