Hey @JuanPabloDiaz ! Love the love you're giving to that team page!
Generally speaking, I liked the low key team page, but at the same time, it might help us having more contributors in the future :)

😱 @cgrail that's a huge number of contributions!

I am getting a bunch of error when running the project locally and I am not sure how to fix it. Please advise.

What's your node version? How are you starting the project?

5438 contribution 😱 @cgrail that's a huge number of contribution!

Yeah, that is a huge number @cgrail. Congrats for the hard work!

I am getting a bunch of error when running the project locally and I am not sure how to fix it. Please advise.

What's your node version?

Node.js v20.11.0

How are you starting the project?

npm start

@JuanPabloDiaz I pushed some small types to remove some errors and my editor auto linted.

Hmm, I'm not sure why you're getting your errors. 🤔
I'm using node v19.8.1 and npm 9.5.1.

I do have a question though: how do you plan to bypass the GitHub rate limitation? Maybe we could have a static file we can generate once in a while? Or piggy back on if GitHub returns a 429?

I do have a question though: how do you plan to bypass the GitHub rate limitation? Maybe we could have a static file we can generate once in a while? Or piggy back on if GitHub returns a 429?

That's a good point! I didn't really consider that as an issue in production. While refreshing during development is normal, typical users wouldn't be reloading that frequently.

The static file will be a good idea in case we get a 429.

That's fair. Whether a static JSON list or even just a message explaining why it's not loading. Or even just not showing the section at all. Whatever you prefer, I don't have a strong opinion here.

I've merged a bunch of dependabot PRs, so you will have to rebase and npm install again.

The build command is still throwing me a bunch of errors regarding import issues.

The way I fix it was by update the tsconfig.json file:

  "include": ["src**"]

I am wondering if that is okey? The errors are gone on my end. 😃

Locally, I'm surprised you get the errors. The errors that are on CI are just prettier. You should be able to get rid of them by running prettier locally.
I tried running npm run lint -- --fix but it didn't fix the issues 🤔

With that being said. I failed rebasing last night, so I dropped it this morning and tried again. After I rebase and fill ALL the conflicts, I merge team and my main branch. is that a problem?

Looking at the changes, things look good. Rebases can definitely be tricky some times. I often find myself just recreating a new PR and porting my commits one by one or something alike.

Is there anything else that I need or could do?

Sorry for the delay @JuanPabloDiaz, I didn't have the change to test that page again locally.
I'll try to do that tonight.

Could you make the build pass? Looks like you have type error at:

TOPICS[x].toLocaleLowerCase(),

Could you make the build pass? Looks like you have type error at:

TOPICS[x].toLocaleLowerCase(),

I am not sure what that means.

But hey, now I have another error. 57 conflicts in package-lock.json. LOL 😮

I fixed some of the build errors and package.json conflicts.

Time to 🚢 !

Thank you for the great work 🙏🏼