mozilla / fx-private-relay / 8da7c3b7-a519-4539-918c-b416afc03320

91%

main: 91%

Build Type

Pull #6193

circleci

Committed by Vinnl

Commit Message

fix MPP-5435: chore(frontend) Webpack to Turbopack

This is the default in Next.js now, so it's probably safest to align
with that.

Some changes I had to do:
- Set up Turbopack to load FTL files as raw strings.
- Add the raw-loader dependency to do so.
- Compensate for Turbopack (at the moment) loading those strings on
  the `default` export property for FTL modules, rather than having
  the complete module be a string.
- Remove the MSW workaround — I no longer received build errors, so that
  no longer appears to be necessary. This seems to align with the
  current package.json of msw, which indeed now no longer sets any
  exports explicitly to `null`.
- Switch to the function-style syntax for :global, since Turbopack
  always uses LightningCSS, which only supports that.
- Hardcode the breakpoints we use, since Turbopack/LightningCSS won't
  support exporting variables from CSS:
  https://github.com/vercel/next.js/issues/88544
- Next.js itself updated next-env.d.ts

Pull Request Pull Request #6193: Switch from Webpack to Turbopack

Run Details

3005 of 3871 branches covered (77.63%)

Branch coverage included in aggregate %.

2 of 6 new or added lines in 2 files covered. (33.33%)

2 existing lines in 1 file now uncovered.

18490 of 19649 relevant lines covered (94.1%)

13.1 hits per line