run compiled codes in production?

[gucheen]

Would you consider adding a TypeScript build step to run the compiled code using Node.js in a production environment?

Given that this is a single-user application, it might run on devices with limited hardware resources. Running the compiled code could improve performance and reduce resource consumption.

I've tested the build process on my fork, requiring only minor modifications, and so far it's working well.

I'm thinking it might be a viable alternative?

Through unreliable testing, it has saved 80-100MB of memory.

[dahlia]

Thanks for the proposal and the implementation work! The idea of running compiled code in production to reduce memory consumption (80-100MB savings) is very appealing, especially for single-user instances on resource-constrained devices.

I reviewed your fork's commit (dc555d0), and the overall approach using esbuild looks good. However, I think a few adjustments would be needed before merging:

Suggested improvements

1. Script roles should be swapped:

   • pnpm run dev should continue using tsx watch for auto-reload during development
   • pnpm run prod should use node dist/server.js to run the compiled code in production
   • Currently, your implementation has these reversed

2. TypeScript configuration:

   • Setting "noImplicitAny": false weakens type safety
   • If there are build errors, they should be fixed properly rather than loosening the type checks
   • Only "outDir": "dist" needs to be added to tsconfig.json

3. Build step:

   • The pnpm run build script looks good
   • Consider adding options like --sourcemap for debugging if needed

4. Other scripts:

   • Utility scripts like pnpm run rebuild-timelines might also benefit from using compiled versions, but that can be addressed separately

Would you be interested in opening a pull request with these adjustments? We'd be happy to review and help refine the implementation. This would be a great performance improvement for Hollo users!