Next.js 11.1

📰 Hacker News · wener

Learn about the new features and improvements in Next.js 11.1, including security patches and build performance enhancements

intermediate Published 12 Aug 2021
Action Steps
  1. Update to Next.js 11.1 using npm or yarn
  2. Review the security patch notes to understand the vulnerabilities addressed
  3. Test your application's build performance to see the improvements
  4. Explore the new features and enhancements in Next.js 11.1
  5. Deploy your updated application to a production environment
Who Needs to Know This

Software engineers and developers who use Next.js can benefit from this update, as it improves build performance and addresses security concerns

Key Insight

💡 Next.js 11.1 improves build performance and addresses security concerns, making it a worthwhile update for developers

Share This
🚀 Next.js 11.1 is out! 🚀 Improved build performance and security patches 🛡️

Key Takeaways

Learn about the new features and improvements in Next.js 11.1, including security patches and build performance enhancements

Full Article

Title: Next.js 11.1

URL Source: https://nextjs.org/blog/next-11-1

Published Time: 2021-08-11T16:00:00.507Z

Markdown Content:
[Skip to content](https://nextjs.org/blog/next-11-1#geist-skip-nav)

[![Image 1: Vercel](https://nextjs.org/_next/static/immutable/media/vercel-light.3_gxxexgi1nmy.svg)![Image 2: Vercel](https://nextjs.org/_next/static/immutable/media/vercel-dark.1f3cgy23m5_jy.svg)](https://vercel.com/home?utm_source=next-site&utm_medium=banner&utm_campaign=blog_next-11-1 "Go to Vercel homepage")[![Image 3: NextjsLogotype](https://nextjs.org/_next/static/immutable/media/nextjs-logotype-light.00-_80jv8_dct.svg)![Image 4: NextjsLogotype](https://nextjs.org/_next/static/immutable/media/nextjs-logotype-dark.3h4a2z2v_dkod.svg)](https://nextjs.org/ "Go to the homepage")

Search documentation...CtrlK Search...⌘K

[![Image 5: Vercel](https://nextjs.org/_next/static/immutable/media/vercel-light.3_gxxexgi1nmy.svg)![Image 6: Vercel](https://nextjs.org/_next/static/immutable/media/vercel-dark.1f3cgy23m5_jy.svg)](https://vercel.com/home?utm_source=next-site&utm_medium=banner&utm_campaign=blog_next-11-1 "Go to Vercel homepage")[![Image 7: NextjsLogotype](https://nextjs.org/_next/static/immutable/media/nextjs-logotype-light.00-_80jv8_dct.svg)![Image 8: NextjsLogotype](https://nextjs.org/_next/static/immutable/media/nextjs-logotype-dark.3h4a2z2v_dkod.svg)](https://nextjs.org/ "Go to the homepage")

[Showcase](https://nextjs.org/showcase)[Docs](https://nextjs.org/docs "Documentation")[Blog](https://nextjs.org/blog)[Templates](https://vercel.com/templates/next.js?utm_source=next-site&utm_medium=navbar&utm_campaign=next_site_nav_templates)[Enterprise](https://vercel.com/contact/sales/nextjs?utm_source=next-site&utm_medium=navbar&utm_campaign=next_site_nav_enterprise)

Search documentation...CtrlK Search...⌘K[![Image 9: Vercel](https://nextjs.org/_next/static/immutable/media/vercel-light.3_gxxexgi1nmy.svg)![Image 10: Vercel](https://nextjs.org/_next/static/immutable/media/vercel-dark.1f3cgy23m5_jy.svg)Deploy](https://vercel.com/new/clone?utm_source=next-site&utm_medium=banner&b=main&s=https%3A%2F%2Fgithub.com%2Fvercel%2Fvercel%2Ftree%2Fmain%2Fexamples%2Fnextjs&template=nextjs&teamCreateStatus=hidden&utm_campaign=blog_next-11-1)[Learn](https://nextjs.org/learn)

[Back to Blog](https://nextjs.org/blog)
Wednesday, August 11th 2021

# Next.js 11.1

Posted by

[![Image 11: DongYoon Kang](https://nextjs.org/_next/image?url=%2Fstatic%2Fteam%2Fkdy.jpg&w=64&q=75&dpl=dpl_8bJFHY6ZUvoxxM66PPUJqPsGKW8X) DongYoon Kang@kdy1dev](https://twitter.com/kdy1dev)[![Image 12: Jiachi Liu](https://nextjs.org/_next/image?url=%2Fstatic%2Fteam%2Fjiachi.png&w=64&q=75&dpl=dpl_8bJFHY6ZUvoxxM66PPUJqPsGKW8X) Jiachi Liu@huozhi](https://twitter.com/huozhi)[![Image 13: JJ Kasper](https://nextjs.org/_next/image?url=%2Fstatic%2Fteam%2Fjj.jpg&w=64&q=75&dpl=dpl_8bJFHY6ZUvoxxM66PPUJqPsGKW8X) JJ Kasper@_ijjk](https://twitter.com/_ijjk)[![Image 14: Maia Teegarden](https://nextjs.org/_next/image?url=%2Fstatic%2Fteam%2Fmaia.jpg&w=64&q=75&dpl=dpl_8bJFHY6ZUvoxxM66PPUJqPsGKW8X) Maia Teegarden@padmaia](https://twitter.com/padmaia)[![Image 15: Shu Ding](https://nextjs.org/_next/image?url=%2Fstatic%2Fteam%2Fshu.jpg&w=64&q=75&dpl=dpl_8bJFHY6ZUvoxxM66PPUJqPsGKW8X) Shu Ding@shuding_](https://twitter.com/shuding_)[![Image 16: Steven](https://nextjs.org/_next/image?url=%2Fstatic%2Fteam%2Fstyfle.png&w=64&q=75&dpl=dpl_8bJFHY6ZUvoxxM66PPUJqPsGKW8X) Steven@styfle](https://twitter.com/styfle)[![Image 17: Tim Neutkens](https://nextjs.org/_next/image?url=%2Fstatic%2Fteam%2Ftim.jpg&w=64&q=75&dpl=dpl_8bJFHY6ZUvoxxM66PPUJqPsGKW8X) Tim Neutkens@timneutkens](https://twitter.com/timneutkens)[![Image 18: Tobias Koppers](https://nextjs.org/_next/image?url=%2Fstatic%2Fteam%2Fsokra.jpg&w=64&q=75&dpl=dpl_8bJFHY6ZUvoxxM66PPUJqPsGKW8X) Tobias Koppers@wSokra](https://twitter.com/wSokra)

We're improving build performance across the entire stack with Next.js 11.1, featuring:

* [**Security Patch**](https://nextj
Read full article → ← Back to Reads