3a7c35a926
The fallback fonts are applied in the wrong order which can cause the generated fallback font not to get applied. ref: [slack](https://vercel.slack.com/archives/C03S8ED1DKM/p1669834408302339?thread_ts=1669765718.933099&cid=C03S8ED1DKM) ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) |
||
---|---|---|
.. | ||
css-loader | ||
next-edge-ssr-loader | ||
next-flight-loader | ||
next-font-loader | ||
next-serverless-loader | ||
next-style-loader | ||
postcss-loader | ||
resolve-url-loader | ||
error-loader.ts | ||
get-module-build-info.ts | ||
next-app-loader.ts | ||
next-client-pages-loader.ts | ||
next-edge-function-loader.ts | ||
next-flight-client-entry-loader.ts | ||
next-flight-css-dev-loader.ts | ||
next-image-loader.js | ||
next-middleware-asset-loader.ts | ||
next-middleware-loader.ts | ||
next-middleware-wasm-loader.ts | ||
next-swc-loader.js | ||
noop-loader.ts | ||
utils.ts |