After intital set up in Docker and running, 'http://localhost:3000/topics' Shows blank page in Edge and Chrome

[mikepoz59]

Describe the bug
Following the instructions on the Readme.MD page, and changing the ENV hosts to "localhost", starting the service and opening the portal works on the default landing page, and then clicking down the left navigation panel icons, everything except "topics" (folder Icon) resolves properly, but the "topics" URL results in a blank page.

To Reproduce
Steps to reproduce the behavior:

1. Run the 'docker-compose -f docker-compose-kafka-prom.yml up -d'
2. Make sure Node.js is installed: v16.13.0
3. Follow the install, and build command sequence.
4. Modify the host name in the .env file to be "localhost".
5. execute "npm start" and wait for the "Kafka Admin Connected" message in the console
6. Launch the portal "http://localhost:3000".
7. Click each of the icons in the left navigation pane.

Expected behavior
Each icon's target will resolve properly in a useful portal page.

Actual behavior
The Topics icon link results in a blank page in both Edge and Chrome browsers. Note, I did not test in other browsers.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 11

• Browser: Edge

• Version: 104.0.1293.70 (Official build) (64-bit)
  
  Edit Note: Uploaded the right screenshot, sorry!

• Browser 2: Chrome

• Version: 104.0.5112.102 (Official Build) (64-bit)
  

Additional context
After the above, I added a topic, and the Topic page did resolve, so perhaps, if there are no topics are found, you should either:

1. Put up a message stating no topics found, please create at least one.
2. Redirect to the "Create a Topic" page automatically.
   Edit Note: Added the additional context once I figured that part out.

[mikepoz59]

Side note, this looks to have amazing potential, and I'm evaluating it for use at work on our team's Kafka clusters.

[rbhastie]

@mikepoz59 Thank you for the feedback and for raising this issue. We will look into this asap!