migrate timezones-list lib to @vvo/tzdb issue #4479

[huzaifaazim0]

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

migrated timezones-list lib to @vvo/tzdb

Fixes #4479

Type of change

non-breaking

Please delete any options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
• My changes generates no new warnings
• My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

[chakflying]

I took a look at the getTimezoneOffset() function in the front-end, and realized that we are currently using the native Date object to obtain the offset of a Timezone, whereas in the back-end we seem to be using dayjs. The original timezones-list is really just that, a list of timezones for the user to pick. I guess I'm not familiar enough with how these things work to know if it would cause issues.

The code change here looks simple enough, haven't the time to test it yet.

[huzaifaazim0]

Hello, Yes you are correct, it's just a list. Please test and let me know if other changes are needed. Thanks.

…

On Mon, Feb 26, 2024, 12:20 PM Nelson Chan ***@***.***> wrote: I took a look at the getTimezoneOffset() function in the front-end, and and realized that we are currently using the native Date object to obtain the offset of a Timezone, whereas in the back-end we seem to be using dayjs. The original timezones-list is really just that, a list of timezones for the user to pick. I guess I'm not familiar enough with how these things work to know if it would cause issues. The code change here looks simple enough, haven't the time to test it yet. — Reply to this email directly, view it on GitHub <#4521 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARUVYRYNTK3LOFHN3FOL4NLYVQZTRAVCNFSM6AAAAABDXD5CXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRTGQ3DENRQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[chakflying]

Tested working okay.

[huzaifaazim0]

Great, thanks It was nice contributing to uptime-kuma Looking forward to solving more issues

…

On Tue, Feb 27, 2024, 10:46 PM Nelson Chan ***@***.***> wrote: ***@***.**** approved this pull request. Tested working okay. — Reply to this email directly, view it on GitHub <#4521 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARUVYRYIUC2FFLWK3AFOXPDYVYLWXAVCNFSM6AAAAABDXD5CXCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSMBUGM2DOOJTGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>