GitHubHeatMap defaults to previous year in NodeJS wiki

[protrolium]

Hello,

I am having an issue with GitHibHeatMap here:
https://gavart.ist/#%24%3A%2Fplugins%2FGk0Wk%2Fecharts%2FSnippets%2FGitHubHeatMap

$:/state/heatmap!!year is equal to 2025

But each time the page is refreshed and the server is started again it defaults to the year 2024. I cannot find what's causing this.

[protrolium]

Has anyone an idea why $:/state/heatmap!!year is not saving properly in NodeJS ? It keeps loading to previous year (2024) even after setting to current year.

[oeyoews]

You should manually delete this tiddler

[protrolium]

I followed your instruction @oeyoews but it doesn't seem to solve the issue. Still defaults to previous year (2024) on hard refresh.

[oeyoews]

I followed your instruction @oeyoews but it doesn't seem to solve the issue. Still defaults to previous year (2024) on hard refresh.

https://gavart.ist/#%24%3A%2Fstate%2Fheatmap Is your online address updated? You need to check the creation or modification time of this state tiddler

[protrolium]

Interesting. In my local NodeJS setup, it appears updating the field of $:/state/heatmap does not preserve the metadata of the tiddler when the site is reloaded. When the field is updated the Updated metadata correctly shows today's date, but upon refresh it reverts and jumps back to 2024. I wonder why this is happening.

[oeyoews]

This should be related to your saving or deployment method. If you save it directly as an HTML, and your tiddler has this state tiddler, this situation will occur

Also, this state tiddler will not be generated by default unless you manually jump to the heatmap year.

[protrolium]

I had to manually delete the tiddler $:/state/heatmap in VSCode, because deleting $:/state/heatmap from within TiddlyWiki didn't seem to have the same effect (it wouldn't actually delete itself). Thank you @oeyoews