archive/rsnext

Author SHA1 Message Date

Author	SHA1	Message	Date
Johannes Obermair	82ed6a3b0d	Fix next/image config injection during static generation (#47007 ) Fixes #39330. I've not added a new test, but extended the existing test instead (and re-enabled it). It seems to me that a custom next/image config was not considered during static generation (which itself uses `next export`?) before. Adding the config to `renderOpts` in `packages/next/src/export/index.ts` resolves the issue.	2023-03-13 10:47:05 -07:00
Steven	241195ddd6	BREAKING CHANGE: Rename `next/image` to `next/legacy/image` & rename `next/future/image` to `next/image` (#41399 ) This PR introduces breaking changes by renaming components. - Rename `next/image` to `next/legacy/image` - Rename `next/future/image` to `next/image` The diff is very confusing because both components are very similar so git got confused.	2022-10-14 01:59:22 +00:00

Johannes Obermair

82ed6a3b0d

Fix next/image config injection during static generation (#47007 )

Fixes #39330.

I've not added a new test, but extended the existing test instead (and
re-enabled it).

It seems to me that a custom next/image config was not considered during
static generation (which itself uses `next export`?) before. Adding the
config to `renderOpts` in `packages/next/src/export/index.ts` resolves
the issue.

2023-03-13 10:47:05 -07:00

Steven

241195ddd6

BREAKING CHANGE: Rename next/image to next/legacy/image & rename next/future/image to next/image (#41399 )

This PR introduces breaking changes by renaming components.

- Rename `next/image` to `next/legacy/image`
- Rename `next/future/image` to `next/image`

The diff is very confusing because both components are very similar so git got confused.

2022-10-14 01:59:22 +00:00

2 commits