Raw ISO date time displayed instead of relative time

[bagasme]

Description

I built Gitea from source on Debian 11 using Go 1.20.3 and Node v18.13.0 (npm 8.19.3). Yesterday I built commit 4299c3b. Before building, I wiped out node_modules directory (as it contains node artifacts). Then I built as usual and deployed to my Gitea instance on LXD container. Previous commit deployed to the instance before the rebuild was commit 57aab79. No app.ini changes between deployments.

The Gitea instance uses PostgreSQL 15.2 on another container.

When I logged in to the instance, I noticed that raw ISO 8601 date time format was displayed instead of usual relative time (e.g. 12 minutes ago) when I browse my repos and also on the dashboard.

I have tried reproducing on try.gitea.io but the issue doesn't occur (as it was deployed from commit 334c899) so either I have issues on my app.ini or this issue had been fixed in more recent commits than I deployed.

Here are gitea.log from my instance and sanitized config.

Screenshots

On the production

On try.gitea.io

Gitea Version

main (commit 4299c3b)

Can you reproduce the bug on the Gitea demo site?

No

Operating System

Ubuntu 22.04

Browser Version

Firefox Developer Edition (113.0.b2)

[wxiaoguang]

The relative-time is related to #23988 (which still has some open issues/PRs)

For the file list, I guess it's related to #24106 @yardenshoham

[yardenshoham]

@bagasme does https://github.com/github/relative-time-element work in your browser? Does https://github.github.io/relative-time-element/examples/ render for you?

@wxiaoguang do we polyfill the JS.Intl APIs?

[yardenshoham]

I was able to reproduce:

I did it by compiling webpack without @github/relative-time-element:

Please make sure you have that package in node_modules

[delvh]

Can this issue be closed then?

[yardenshoham]

Let's make sure @bagasme fixed their issue

[bagasme]

Issue fixed by checking node_modules to contain appropriate module as @yardenshoham said. Closing.