create-react-app-buildpack VS heroku-buildpack-jemalloc

I just started learning React and have been deploying to Heroku since it has worked the best in the past. I saw that the most popular build pack will soon no longer work as Heroku is upgraded. What does this mean for the future of React projects on Heroku?

Once you click add buildpack, it displays a pop-up on the dashboard. Paste this link in the Enter Buildpack URL and click on save changes. That is all you have to do.

https://github.com/mars/create-react-app-buildpack.git

the 405 is being thrown by the nginx reverse proxy that's run as part of the community create-react-app buildpack for heroku. I haven't dug in deeply but I'm assuming you're using this and that'd be the place to start. there's some noise about 405s being 'disallowed' for builds using Heroku's static buildpack (which this one does), but I have no idea why, how or if that's actually the case. good luck

I'm not sure you need a dyno for React as it runs in a user's browser. You just need a way to serve the JS to your user. After a quick google search I found this article and this Heroku buildpack. Good luck

Using jemalloc instead of regular malloc helps too. The exact way to do this depends on the platform you use, but it is pretty simple on Heroku. Just set heroku-buildpack-jemalloc as the first buildpack (ahead of the heroku/ruby buildpack).

I've recently discovered jemalloc, specifically when used with Heroku.

"Using jemalloc instead of regular malloc helps too. The exact way to do this depends on the platform you use, but it is pretty simple on Heroku. Just set heroku-buildpack-jemalloc as the first buildpack (ahead of the heroku/ruby buildpack)."

FYI, remember to set JEMALLOC_ENABLED=true in your env to actually turn it on.

https://github.com/gaffneyc/heroku-buildpack-jemalloc

Like I mentioned earlier, Digital Ocean App Platform uses the same buildpacks as Heroku to deploy your apps. This means that most apps that can be deployed on Heroku should also be deployed on Digital Ocean. There is one big caveat, though; you can't select which buildpack(s) to use. This means you have to rely on Digital Ocean to pick the right ones for your project. It also gives you a bit less flexibility in how your app runs. For instance, I recently configured our app at work to run using jemalloc, a malloc alternative that often has better performance for Ruby apps. We did that via a buildpack heroku-buildpack-jemalloc, which allowed us to switch to jemalloc without any app changes. Customizations to the build environment like this don't seem possible given the Digital Ocean App Platform's current offerings.