Re:Porting a React Front End to TypeScript
by czei002 on Tuesday April 28, 2020 @05:17PM
(#23012170)
Thanks for sharing! We actually tried the same approach but we have a couple of more micro services relying on the same shared code. This has some additional complications, e.g. managing all dependencies for all services in one package.json is a bit messy and preparing a pkg for deployment gets a bit more complicated...
[ Parent
| on HN ]
Re:Porting a React Front End to TypeScript
by gary_bernhardt on Tuesday April 28, 2020 @07:32PM
(#23013447)
Ahh, if you're taking the microservice path then you're going to have to fight all of that complexity. So far we've stuck to the constraints that I set at the beginning of the project: vanilla Heroku web dynos; exactly one Heroku worker dyno (never 0 or 2); and Postgres is the only data store (no queues etc.)