serve VS create-react-app-buildpack

The above code starts a static server (Vercel’s serve) in port 3000. Open the URL in Chrome, open the DevTools, and click the Source tab. You’ll see main.ts as follows:

Another alternative that comes to my mind it is to use the node.js buildpack and serve the static files using serve or similar.

If you don't know how to create a backend, you can try https://npmjs.com/package/serve which is a command that will run a simple server that just serves you the files in a folder (kinda like /public does) but it runs separately from CRA/Webpack so will not affect your app. You then have to take care of fetching and updating the data with fetch() as often as you need.

In app.jsx I've tried removing all the root code and just rendered a typical "Hello World" p tag and it doesn't take nearly as long. I've also ran a basic web server infront of the build folder using serve which suggests it might webpack-dev-server that is having issues with the size of the application (Or could it be saying it's built before it actually is?).

Maybe I was lacking context a bit. I was referencing this actually: https://github.com/vercel/serve/pull/680

https://github.com/vercel/serve (nodejs implementation, therefore requires npm or yarn being installed which are package managers for node)

React.js/ Next.js / Material-UI / Browserify (bundle packaging) / Serve (static site serving) / React-Dropzone (file drag drop) / React-Idle-Timer / zxcvbn.js (Password strength estimation)

https://github.com/vercel/serve (that one should run on every system since it's implemented in NodeJS)

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