Changes for new release

[KristjanESPERANTO]

As discussed in #341, I have collected changes for the next release here.

My goal for the next release is to take care of low-hanging fruits first. This mainly includes adopting existing easy-to-understand PRs, updating the toolchain a bit and fixing small flaws found along the way.

Major changes and handling reported issues I would plan for after the next release. Steps like these are what I would consider major changes:

• Replace tools in the toolchain
• Sharpening the ESLint rules incl. handling the reported issues (this will cause a lot of changes)
• Switch from CommonJS to ESM

I will leave comments on some of the commits here:

Merged PRs

• Add Chinese Mainland PH #406
• Create na.yaml #452
• Add holy friday and Carnival days of Argentina. #456
• Add SH for be for 2024-2026 #457
• Add Luxembourg holidays #460
• Correct Swedish and Finnish public holidays #465
• Update Hungarian school holidays #466

Solved issues

• Table in evaluation tool has issues when zoom is less than 100 % (for example 90 %) #419 - commit 5ea11a2

Not merged PRs

• [Evaluation tool] Optimize "Error and warning messages" layout #469 - I would merge it, but I would like to wait for feedback from you.
• Bugfix/Workaround for issue #319: split group_value by ',' for replac… #320 - Needs work.
• Add Scotland and Northern Ireland public holidays #415 - I would merge it, but there is an unanswered question.
• Add JE (PH) #424 - It's a draft.
• try to clarify 24/7 description #453 - It's just a small change and seems okay, but I'd rather know what you think.

🎆 Running CI with maintained node versions 82d534a

I had to update husky and rework ci.yml for this.

🐞 Fix 'yamlToJson.mjs' 2d28f1c

• Add missing process import
• Sort imports
• Replace 'prettier' by internal function
• Add console output

Side note: I don't know where the script is used. I noticed during the review that it uses prettier and that prettier is not in the package.json.

Nits

There are some nits like

• Updating URLs
• Updating copyright years

Thoughts

After some work on this PR, I think it would have been clearer if I had written my additional changes in separate PRs and used this one as a collector for them.

[KristjanESPERANTO]

@ypid: Before I go any further, can you please check if I'm going in the right direction here? My next step would be to review and (if ok) merge more PRs.

[KristjanESPERANTO]

I think it's more than enough for a release now. Let me know if you don't like anything.

[ypid]

@KristjanESPERANTO Thanks very much for all your work! I am currently working on a private project in my spare time which should be completed by the end of January, then I will pick up this. Sorry for the delay.

Edit: I will work on this 2025-03-29 -- 30 beginning of 2025-04. Sorry again for the delay. And thanks for your patience!

[KristjanESPERANTO]

No problem, there's no hurry 🙂

[KristjanESPERANTO]

If a rebase helps you to review it or anything else, let me know.