3ad55721d1
**Reasons for making this change:**
- it is contained within `node_modules/`, which is already ignored
- the previous versions, which were not in `node_modules/`, did not have
a period at the beginning of the filename
Links to documentation supporting these rule changes:
**Changelog with proof here:**
|
||
---|---|---|
.. | ||
components | ||
pages | ||
public | ||
.gitignore | ||
app.css | ||
next-env.d.ts | ||
next.config.js | ||
package.json | ||
README.md | ||
styles.module.css | ||
tsconfig.json |
Legacy Image Component Example
This example shows how to use the Legacy Image Component in Next.js serve optimized, responsive images.
The index page (pages/index.js
) has a couple images, one internal image and one external image. In next.config.js
, the domains
property is used to enable external images. The other pages demonstrate the different layouts. Run or deploy the app to see how it works!
Live demo
https://image-legacy-component.nextjs.gallery
Deploy your own
Deploy the example using Vercel or preview live with StackBlitz
How to use
Execute create-next-app
with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example image-legacy-component image-app
# or
yarn create next-app --example image-legacy-component image-app
# or
pnpm create next-app --example image-legacy-component image-app
Deploy it to the cloud with Vercel (Documentation).