umami: An `id` must be provided to format a message.

Describe the Bug

using umami image: ghcr.io/umami-software/umami:postgresql-v2.3.1 and postgres:15-alpine

[@formatjs/intl] An `id` must be provided to format a message. You can either: 1. Configure your build toolchain with [babel-plugin-formatjs](https://formatjs.io/docs/tooling/babel-plugin) or [@formatjs/ts-transformer](https://formatjs.io/docs/tooling/ts-transformer) OR 2. Configure your `eslint` config to include [eslint-plugin-formatjs](https://formatjs.io/docs/tooling/linter#enforce-id) to autofix this issue
Error: [@formatjs/intl] An `id` must be provided to format a message. You can either:
1. Configure your build toolchain with [babel-plugin-formatjs](https://formatjs.io/docs/tooling/babel-plugin)
or [@formatjs/ts-transformer](https://formatjs.io/docs/tooling/ts-transformer) OR
2. Configure your `eslint` config to include [eslint-plugin-formatjs](https://formatjs.io/docs/tooling/linter#enforce-id)
to autofix this issue
    at ep (https://statistic.wokalek.ru/_next/static/chunks/pages/_app-d25b7d6c3a248600.js:1:160)
    at eE (https://statistic.wokalek.ru/_next/static/chunks/pages/_app-d25b7d6c3a248600.js:6:577936)
    at e4 (https://statistic.wokalek.ru/_next/static/chunks/pages/_app-d25b7d6c3a248600.js:6:587683)
    at q (https://statistic.wokalek.ru/_next/static/chunks/pages/websites/%5Bid%5D-549d2825f0ffde57.js:1:4501)
    at ab (https://statistic.wokalek.ru/_next/static/chunks/framework-2c79e2a64abdb08b.js:9:60915)
    at ud (https://statistic.wokalek.ru/_next/static/chunks/framework-2c79e2a64abdb08b.js:9:72801)
    at i (https://statistic.wokalek.ru/_next/static/chunks/framework-2c79e2a64abdb08b.js:9:120370)
    at oO (https://statistic.wokalek.ru/_next/static/chunks/framework-2c79e2a64abdb08b.js:9:99112)
    at https://statistic.wokalek.ru/_next/static/chunks/framework-2c79e2a64abdb08b.js:9:98979
    at oF (https://statistic.wokalek.ru/_next/static/chunks/framework-2c79e2a64abdb08b.js:9:98986)

Database

PostgreSQL

Relevant log output

No response

Which browser are you using? (if relevant)

Chrome

How are you deploying your application? (if relevant)

docker

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 17 (3 by maintainers)

Most upvoted comments

Also randomly started having this issue on 2.3.0. Works on 2.4.0.

I also have this problem. Before deploying the v1 version with dockers, this problem did not occur. Now I use vercel to deploy the v2 version. This problem occurs. I have a headache and ask for help.

Try update to 2.4.0.