What do you think?
Rate this book
Next.js Cookbook: Learn how to build scalable and high-performance apps from scratch
Practical solutions and proven recipes for building dynamic web applications with Next.js Key Features ● Learn how to develop an Enterprise Resource Planning (ERP) application using Next.js. ● Learn how to use design patterns in Next.js effectively. ● Learn how to implement server-side rendering for improved performance. Description Next.js is a powerful and flexible framework for building server-side rendered React applications. In this book, you will learn how to develop a full-stack ERP application from scratch to production using Next.js. The book will begin by covering the basics of Next.js, including setting up the environment and creating your first app. You will then learn how to use design patterns to optimize the application development process. Next, the book will help you get familiar with Next.js's server-side rendering capabilities by providing the knowledge and skills needed to leverage this powerful feature to improve the performance and user experience of your ERP application. You will also learn to manage the complex application state using Redux, as well as how to implement internal pages and create a CRUD system for user data. In addition, the book will help you perform end-to-end testing using Cypress and Playwright, and deploy your application to production using AWS Amplify. Lastly, you will learn how to optimize your web application for search engines, enabling better visibility and higher traffic to your website. By the end of the book, you will be able to develop high-quality web applications using Next.js. What you will learn ● Learn how to use Redux for state management in your Next.js applications. ● Learn how to create pages in Next.js with ease. ● Learn how to write end-to-end tests for your app. ● Learn how to deploy your application to production using AWS Amplify. ● Learn how to use optimization tools to improve the SEO of your application. Who this book is for This book is for anyone interested in learning how to develop full-stack web applications using Next.js. It is also for technical architects, project managers, and other professionals who want to gain a deeper understanding of the technologies and best practices involved in building modern web applications. Table of Contents 1. Warming up with NextJS 2. Using design patterns in NextJS 3. Authorization in a glance with NextJS 4. Server-side power of NextJS 5. Using state management in NextJS 6. Implementing internal pages using NextJS 7. The superpower of E2E testing in NextJS 8. Deploying NextJS project to production 9. Mastering optimization tools for NextJS
270 pages, Paperback
Published May 18, 2023
1 person want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
June 12, 2023
I sincerely regret spending time trying to read this "book".
There's a non-exhaustive list of what you'll encounter (sadly encountered if you're like me);
- The book is simply full of misspellings. I don't know how something like this can be advertised for sale.
- This editorial has hundreds of books. How can not they have a proofreading process? I could accept a couple of typos per chapter, but here every sentence has an error.
- The files used/edited don't have a clear path which results confusing and is prone to errors.
- The code is shared as images.
- Why? Why? This makes the ebook huge with no gain.
- Syntax highlight in the code from the images is completely broken.
- The author does not share the versions of the libraries used.
- You start a project simply by installing libraries as in `npm ...` but no version is ever shared and the package.json is simply non-existent.
- It won't hurt to have a single commented line at the top of every piece of code showing the name of the file being updated.
- The code is not consistent (sometimes you see double quotes, other times single quotes, semicolons yes, other times why bother)
- The code is updated but it's never communicated.
- Some parts of the code are simply wrong, changes done to other parts in the code is not communicated leaving you to figure out what and where's the error.
- To use `toBeInTheDocument` you need to first import `@testing-library/jest-dom`, this is nowhere told.
- Code simply disappears from files
- The content of the book is not well structured.
- Starting by writing code that will be deleted or discarded afterward without any mention.
- What happened with the indentation (?)
Perhaps the only part worth reading is the only chapter about optimization.
I hope I was the only one that had to go through this. I don't advise getting this book, nor reading it even if it's for free.
I don't know the author. But I sincerely hope he keeps writing, may this not be something to stop but to improve (and surely sign with a different editorial).
There's a non-exhaustive list of what you'll encounter (sadly encountered if you're like me);
- The book is simply full of misspellings. I don't know how something like this can be advertised for sale.
- This editorial has hundreds of books. How can not they have a proofreading process? I could accept a couple of typos per chapter, but here every sentence has an error.
- The files used/edited don't have a clear path which results confusing and is prone to errors.
- The code is shared as images.
- Why? Why? This makes the ebook huge with no gain.
- Syntax highlight in the code from the images is completely broken.
- The author does not share the versions of the libraries used.
- You start a project simply by installing libraries as in `npm ...` but no version is ever shared and the package.json is simply non-existent.
- It won't hurt to have a single commented line at the top of every piece of code showing the name of the file being updated.
- The code is not consistent (sometimes you see double quotes, other times single quotes, semicolons yes, other times why bother)
- The code is updated but it's never communicated.
- Some parts of the code are simply wrong, changes done to other parts in the code is not communicated leaving you to figure out what and where's the error.
- To use `toBeInTheDocument` you need to first import `@testing-library/jest-dom`, this is nowhere told.
- Code simply disappears from files
- The content of the book is not well structured.
- Starting by writing code that will be deleted or discarded afterward without any mention.
- What happened with the indentation (?)
Perhaps the only part worth reading is the only chapter about optimization.
I hope I was the only one that had to go through this. I don't advise getting this book, nor reading it even if it's for free.
I don't know the author. But I sincerely hope he keeps writing, may this not be something to stop but to improve (and surely sign with a different editorial).
Displaying 1 of 1 review