@furkan811
Ok, so I’m pretty sure I figured out what the issue here is. At least this definitely solved it for me.
As I got into it more and more and read @k0872 post about how the config.js file was 404ing. I was confused about why that file was even being called so I started looking into the compiled.js file that is actually being called in my wp-admin area. Of course as you know it is using source maps. Previously I had a similar issue with css source maps not working correctly after being packaged for production. It was missing dependencies.
So moral of the story, I SSH into my server and cd into the cloudflare plugin folder. Run composer update, activate the plugin, enter my credentials, works flawlessly. Don’t even need the hotfix that was posted above.
So anyone with this issue and shell access to their server:
install composer (if you don’t already have it)
https://getcomposer.org/doc/00-intro.md#installation-linux-unix-osx
composer update
Activate the plugin
Enter your credentials
Either your lock file is out of date before you are packaging for production or your packaging script isn’t setting up the source maps correctly.