moreminimore-chat

Author SHA1 Message Date

Author	SHA1	Message	Date
Rian Polonini	b126621b3b	perf: load i18n messages on demand in vitest setup (#15291 ) ## Description `vitest.setup.js` runs for every spec file and builds the i18n instance from the full message catalogue, so each of the 389 spec files resolves and transforms the 2537 JSON files under `app/javascript/dashboard/i18n/locale/`. With `pool: 'threads'`, that cost is paid per worker. The result is that `setup` takes about 60x longer than the tests themselves. Only one spec in the suite asserts on translated copy. This PR leaves the global i18n instance without messages and adds `withFullI18n`, an opt-in helper for the specs that need the real catalogue. On this repository's own CI, `setup` drops from ~629s to ~71s (-89%) and total Vitest duration from ~388s to ~196s (-49%). This is a performance and testability change, not a cosmetic one. It touches only how the test harness loads messages — no translatable string and no locale file is modified, so nothing changes for Crowdin contributors. Worth noting: `vitest.config.ts` already excludes `/i18n//` from coverage, so loading the catalogue in every spec was not serving any metric. Fixes #15290 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? ### On this repository's CI The numbers below come from the `test` job of `frontend-fe.yml` on GitHub Actions — this repo's own runners, not a local machine. Baseline is 60 successful `develop` runs* (23–31 Jul 2026), parsed from the Vitest summary line in each job log. \| Vitest metric \| `develop` (n=60) \| This PR \| Delta \| \|---\|---\|---\|---\| \| setup \| median 629s (min 329 / p25 607 / p75 641 / max 680) \| 71s \| -559s (-89%) \| \| duration \| median 388s (min 205 / p25 371 / p75 393 / max 418) \| 196s \| -192s (-49%) \| None of the 60 `develop` runs beat this PR on either metric. Same commit, both on this repo's CI: ``` develop @ `bc7ae88` Test Files 389 passed (389) Duration 323.35s (transform 13.75s, setup 522.48s, collect 42.53s, tests 9.02s, environment 187.05s, prepare 32.77s) this PR Test Files 389 passed (389) Duration 196.20s (transform 18.18s, setup 70.67s, collect 65.97s, tests 12.22s, environment 251.28s, prepare 43.90s) ``` `setup` is the metric that isolates this change: it is a sum of work, so it is not distorted by how fast a given runner happens to be. `duration` improves less because it also covers transform, collect and environment, which this change does not touch. One caveat if you compare total job times instead: on this PR's run, `ruby/setup-ruby` took 130s versus 11s on the baseline (an unrelated cache miss), which hides most of the gain at job level. ### Locally `pnpm exec vitest run`, twice per scenario, on `develop` at `bc7ae88` (Node 24.18.1, macOS arm64): \| \| setup \| duration \| \|---\|---\|---\| \| before \| 373s / 412s \| 60.8s / 67.8s \| \| after \| 40.5s / 42.8s \| 28.1s / 28.5s \| Identical pass/fail counts before and after. Locally there is one failure in both scenarios, pre-existing on `develop` and unrelated to this change: `useReportMetrics.spec.js` expects `'5,000'` and receives `'5.000'`, a thousands-separator difference that depends on the machine locale. It does not occur on CI, where the suite is fully green (389/389). `MacroProperties.spec.js` was the only spec that depended on the global catalogue — it asserts the real copy from `macros.json`. It now calls `withFullI18n()` and keeps asserting the same strings, so coverage of that copy is preserved. ## Notes for reviewers - The `test-i18n` alias was added to `vitest.config.ts` rather than to `vite.shared.ts`, to keep it out of the production build. - `missingWarn: false` and `fallbackWarn: false` were added to the global instance so specs that render translated components without opting in do not flood the output with missing-key warnings. - Any future spec that needs the real copy just calls `withFullI18n()` at the top of the file. ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works (no new test: this is a performance change, verified by the CI measurements above and by the unchanged pass/fail counts) - [x] New and existing unit tests pass locally with my changes - [x] Any dependent changes have been merged and published in downstream modules Co-authored-by: Shivam Mishra <scm.mymail@gmail.com>	2026-08-03 15:08:01 +05:30
Shivam Mishra	170b64d1f1	chore: upgrade to vite 6 (#14363 ) Upgrades the frontend toolchain to Vite 6 and tidies up the build config along the way. Behavior is unchanged for end users; this is dev/build infra. ## What changed - `vite` 5.4 → 6.4, `@vitejs/plugin-vue` → 5.2, `vite-plugin-ruby` → 5.2 (with matching `vite_rails`/`vite_ruby` gem bumps). - Dropped the `vite-node` 2.0.1 pnpm override — no longer needed now that vitest 3 runs on Vite 6 directly. - Split the single `vite.config.ts` into: - `vite.config.ts` (app), `vite.lib.config.ts` (SDK), `vite.shared.ts` (aliases / Vue options), `vitest.config.ts` (tests). - `pnpm build:sdk` now selects the SDK config explicitly instead of branching on `BUILD_MODE=library`. SDK output path is unchanged (`public/packs/js/sdk.js`). No changes needed to Docker images, deployment scripts, or CI — Node 24 and pnpm 10 are already past Vite 6's floor, and the rake `assets:precompile` hook still drives the SDK build via `pnpm`. ## How to test - `pnpm dev` and verify the dashboard, widget, and survey routes load and HMR works. - Load a Chatwoot site widget on a test page and confirm `sdk.js` is served and the widget mounts. - `RAILS_ENV=production bundle exec rake assets:precompile` and confirm `public/packs/js/sdk.js` plus the rest of the manifest are produced. - `pnpm test` for the JS suite. --------- Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> Co-authored-by: Sony Mathew <2040199+sony-mathew@users.noreply.github.com>	2026-06-02 17:01:37 +05:30

Rian Polonini

b126621b3b

perf: load i18n messages on demand in vitest setup (#15291 )

## Description

`vitest.setup.js` runs for every spec file and builds the i18n instance
from the full message catalogue, so each of the 389 spec files resolves
and transforms the 2537 JSON files under
`app/javascript/dashboard/i18n/locale/`. With `pool: 'threads'`, that
cost is paid per worker. The result is that `setup` takes about **60x
longer than the tests themselves**.

Only one spec in the suite asserts on translated copy. This PR leaves
the global i18n instance without messages and adds `withFullI18n`, an
opt-in helper for the specs that need the real catalogue.

**On this repository's own CI, `setup` drops from ~629s to ~71s (-89%)
and total Vitest duration from ~388s to ~196s (-49%).**

This is a performance and testability change, not a cosmetic one. It
touches only how the test harness loads messages — **no translatable
string and no locale file is modified**, so nothing changes for Crowdin
contributors.

Worth noting: `vitest.config.ts` already excludes `**/i18n/**/*` from
coverage, so loading the catalogue in every spec was not serving any
metric.

Fixes #15290

## Type of change

- [x] Bug fix (non-breaking change which fixes an issue)

## How Has This Been Tested?

### On this repository's CI

The numbers below come from the `test` job of `frontend-fe.yml` on
GitHub Actions — this repo's own runners, not a local machine. Baseline
is **60 successful `develop` runs** (23–31 Jul 2026), parsed from the
Vitest summary line in each job log.

| Vitest metric | `develop` (n=60) | This PR | Delta |
|---|---|---|---|
| **setup** | median **629s** (min 329 / p25 607 / p75 641 / max 680) |
**71s** | **-559s (-89%)** |
| **duration** | median **388s** (min 205 / p25 371 / p75 393 / max 418)
| **196s** | **-192s (-49%)** |

None of the 60 `develop` runs beat this PR on either metric.

Same commit, both on this repo's CI:

```
develop @ bc7ae88   Test Files 389 passed (389)
                    Duration 323.35s (transform 13.75s, setup 522.48s, collect 42.53s,
                                      tests 9.02s, environment 187.05s, prepare 32.77s)

this PR             Test Files 389 passed (389)
                    Duration 196.20s (transform 18.18s, setup 70.67s, collect 65.97s,
                                      tests 12.22s, environment 251.28s, prepare 43.90s)
```

`setup` is the metric that isolates this change: it is a sum of work, so
it is not distorted by how fast a given runner happens to be. `duration`
improves less because it also covers transform, collect and environment,
which this change does not touch.

One caveat if you compare total job times instead: on this PR's run,
`ruby/setup-ruby` took 130s versus 11s on the baseline (an unrelated
cache miss), which hides most of the gain at job level.

### Locally

`pnpm exec vitest run`, twice per scenario, on `develop` at `bc7ae88`
(Node 24.18.1, macOS arm64):

| | setup | duration |
|---|---|---|
| before | 373s / 412s | 60.8s / 67.8s |
| after | 40.5s / 42.8s | 28.1s / 28.5s |

Identical pass/fail counts before and after. Locally there is one
failure in both scenarios, pre-existing on `develop` and unrelated to
this change: `useReportMetrics.spec.js` expects `'5,000'` and receives
`'5.000'`, a thousands-separator difference that depends on the machine
locale. It does not occur on CI, where the suite is fully green
(389/389).

`MacroProperties.spec.js` was the only spec that depended on the global
catalogue — it asserts the real copy from `macros.json`. It now calls
`withFullI18n()` and keeps asserting the same strings, so coverage of
that copy is preserved.

## Notes for reviewers

- The `test-i18n` alias was added to `vitest.config.ts` rather than to
`vite.shared.ts`, to keep it out of the production build.
- `missingWarn: false` and `fallbackWarn: false` were added to the
global instance so specs that render translated components without
opting in do not flood the output with missing-key warnings.
- Any future spec that needs the real copy just calls `withFullI18n()`
at the top of the file.

## Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my code
- [x] I have commented on my code, particularly in hard-to-understand
areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works (no new test: this is a performance change, verified by
the CI measurements above and by the unchanged pass/fail counts)
- [x] New and existing unit tests pass locally with my changes
- [x] Any dependent changes have been merged and published in downstream
modules

Co-authored-by: Shivam Mishra <scm.mymail@gmail.com>

2026-08-03 15:08:01 +05:30

Shivam Mishra

170b64d1f1

chore: upgrade to vite 6 (#14363 )

Upgrades the frontend toolchain to Vite 6 and tidies up the build config
along the way. Behavior is unchanged for end users; this is dev/build
infra.

## What changed
- `vite` 5.4 → 6.4, `@vitejs/plugin-vue` → 5.2, `vite-plugin-ruby` → 5.2
(with matching `vite_rails`/`vite_ruby` gem bumps).
- Dropped the `vite-node` 2.0.1 pnpm override — no longer needed now
that vitest 3 runs on Vite 6 directly.
- Split the single `vite.config.ts` into:
- `vite.config.ts` (app), `vite.lib.config.ts` (SDK), `vite.shared.ts`
(aliases / Vue options), `vitest.config.ts` (tests).
- `pnpm build:sdk` now selects the SDK config explicitly instead of
branching on `BUILD_MODE=library`. SDK output path is unchanged
(`public/packs/js/sdk.js`).

No changes needed to Docker images, deployment scripts, or CI — Node 24
and pnpm 10 are already past Vite 6's floor, and the rake
`assets:precompile` hook still drives the SDK build via `pnpm`.

## How to test
- `pnpm dev` and verify the dashboard, widget, and survey routes load
and HMR works.
- Load a Chatwoot site widget on a test page and confirm `sdk.js` is
served and the widget mounts.
- `RAILS_ENV=production bundle exec rake assets:precompile` and confirm
`public/packs/js/sdk.js` plus the rest of the manifest are produced.
- `pnpm test` for the JS suite.

---------

Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com>
Co-authored-by: Sony Mathew <2040199+sony-mathew@users.noreply.github.com>

2026-06-02 17:01:37 +05:30

2 Commits