Hi! You pushing your whole project to heroku is there any downsides to it when project becomes quite large? Is there a way to push only the final build?
So NX could keep track of what you've already built, return the result of that and only build new code changes. Basically you would never need to rebuild the same code twice.
Hi! You pushing your whole project to heroku is there any downsides to it when project becomes quite large? Is there a way to push only the final build?
Hello Alex,
So NX workspaces has this quite cool concept that is called Computation Caching that you can use with their NX Cloud service.
So NX could keep track of what you've already built, return the result of that and only build new code changes. Basically you would never need to rebuild the same code twice.
Here is a article describing it more in detail
Computation Caching | The Fundamentals Behind Nx’s Lightning Fast Execution
This is a great free resource if you are interested in getting into the nuts & bolts of NX workspaces
Scale React Development with Nx