fa5d41b346
## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added Fixes #25207 Currently rewritten routes that use a `has` condition throw an `Object.fromEntries is not a function` error in older browsers. ## Documentation / Examples - [x] Make sure the linting passes ## Solution As mentioned in issue #25207, looks like last year the team decided not to include the `fromEntries` polyfill https://github.com/vercel/next.js/pull/15772#discussion_r463957221. As such, we should avoid using non-polyfilled methods in core next.js code bundled in the browser. This PR's changes should result in the same object being returned, without using `fromEntries`. |
||
---|---|---|
.. | ||
i18n | ||
router | ||
amp-context.ts | ||
amp.ts | ||
constants.ts | ||
document-context.ts | ||
dynamic.tsx | ||
head-manager-context.ts | ||
head.tsx | ||
loadable-context.ts | ||
loadable.d.ts | ||
loadable.js | ||
mitt.ts | ||
post-process.ts | ||
router-context.ts | ||
runtime-config.ts | ||
side-effect.tsx | ||
to-base-64.ts | ||
utils.ts |