State of codestream

[gbowne1]

Well now, let's see how do I best describe the state of codestream as of Mid February 2026.

We've gotten up to the point where we've hit a lot of back and forth CI issues.

There's currently a number of open PRs that:

• Need more review by at least one more collaborators
• Need rebase
• Need merge conflicts resolved
• Need merge especially Add Real-Time Chat Functionality with Socket.io #68

We're having issues due to several monolithic files like server.js and main.js

We should aim to be less monolithic so that changes by several contributors:

• won't break CI
• easier to maintain
• more separated concerns
• might be somewhat easier to test

#68 needs review so I can get the last bit ot live stream functionality in

As still some measure of safety I'm only merging PRs that have at least 2 other approved reviews that show ✅ next to the reviewer on github. Won't need to do that so much when we have passing CI, passing tests, less monolithic structures, seoa

We will need to work on separating the frontend from the backend code. Use #77 #78

Then we can work on adding more to the backend and server and APIs. I created a bunch of issues marked TODO staring with issue #100 through #104 which would add more to the backend

Screenshots of the entire app need to go into #67 perhaps short videos or clips so we can document

There is still a ton of duplicate code in the repository due to the fact we're having so many problems with merge conflict's and monolithic structures etc. I don't even know if it will run probably? without major work?

There's been some AI contribution happening. We'll have to address that soon.
I'm okay with using AI to help debug this application but not so keen on using it for broad generation of code. Some small amount of generated Boilerplate code is okay though to reduce the overall amount of typing.required.

I merged some of the live functionality in PR #61 it will need #68 added to it in order for this project to become even slightly useable.

I'd also like to suggest we start doing preflight precommit procedures before we push a commit for PR. Maybe use husky?

@Ved178 @gbowne1 @shishir-21 @EdoAbarca @Haseebx162006 @glenjaysondmello

[shishir-21]

@gbowne1

Thanks for the detailed update on the current state of the project.
I agree that the monolithic structure in server.js and main.js is likely contributing to CI failures and merge conflicts.

I’d be happy to help with refactoring efforts to modularize the backend (separating routes, controllers, and services) to reduce duplication and make the codebase easier to maintain.

I can also review PR #68 to help move the live stream functionality forward.

Setting up pre-commit checks (like Husky) sounds like a good idea to prevent CI issues before pushing PRs — I can look into that as well if needed.

Let me know where you'd prefer I start.

[gbowne1]

@shishir-21

You've already reviewed it before a couple of times so I will let that stand unless you want to re-review it I can request a new review

The workflow from commit to commit through multiple PRs, and still maintaining a stable project isn't easy. We are getting there.

I suppose we could just merge open PRs but in my opinion that carries risks

The monolithic structures we had were fine when we didn't have many contributors or much functionality. I'll take the blame for that.

Yes please review #68

Its becoming increasingly important for our collaborators and maintainers and contributors to use at minimum the eslint and prettier npm scripts before the commit and push code to the PR. Wish there was a great way to ensure its correct even before the workflow runs and that they both agree with each other

As far as where you can start is

[gbowne1]

Well, CodeByStella closed their RTC PR #68

So that needs redoing because they deleted their head then closed it

[gbowne1]

Not particularly sure what to do about that.

@shishir-21 I might take on #99 if thats okay with you and I'll use the structure in the issue.

Someone can do #100 and the rest of the backend Todo list #101 #102 #103 etc

[gbowne1]

Well, yesterday I added a PR to make style.css more flexible and modular and less monolithic.
Reducing the chances of PR overlap to fix css or add to it also less CI failures.

I didn't do a prettier run or eslint on it so theres that but usually css code style issues don't happen very often

It's also more maintainable and easier to add new things or debug.

I also added a PR that fixes the index.html that had two layers of duplicate stuff.

I'd suggest merging those soon.

Well CodeByStella deleted their PRs for functionality without it getting merged.

Just minor package issues causing CI to fail.

Should have been through this already but 🤷‍♂️
Itll be okay once we're less monolithic.

[gbowne1]

You have an open PR. It was a good attempt. I know you attempted to clean up the CI.

Should we wait till the refactoring is finished to fix the CI?

[shishir-21]

We should wait for the refactoring to be completed. After that, we can fix the CI.

[gbowne1]

I'm inclined to do #100 first then what's outlined in #77 #78.

Have you synced/updated yet?

It should render although I have not paid much attention to the actual rendering since we have had so many issues.

[gbowne1]

I can start doing #100 myself if someone wants to take #77 and #78 following this. Otherwise I think we'll keep having the same issues till it gets finished refactoring.

It'll mean we largely ignore CI though.

But I'm completely comfortable doing the server and main.js expansion into a backend "app" myself

Oh, btw @shishir-21 https://github.com/gbowne1/RadioLogger need help if you want to

[shishir-21]

@gbowne1
Thanks for the invite! I’d be happy to help.
I can take a look at #77 and #78 while you work on #100.
Let me sync with the latest changes and get started.