Optimizing Next.js Applications With Nx
About The Author
Melvin is a MERN stack developer, technical author, and blockchain enthusiast. He enjoys community building, mentorship and video games.
Nx is a build framework that facilitates optimization, efficient scaling of applications, and other features such as shared libraries and components. In this article, we will be looking at how we can effectively scale Next.js applications by using Nx.
In this article, we will go through how to optimize and build a high-performance Next.js application using Nx and its rich features. We will go through how to set up an Nx server, how to add a plugin to an existing server, and the concept of a monorepo with a practical visualization.
If you’re a developer looking to optimize applications and create reuseable components across applications effectively, this article will show you how to quickly scale your applications, and how to work with Nx. To follow along, you will need basic knowledge of the Next.js framework and TypeScript.
What Is Nx?
Nx is an open-source build framework that helps you architect, test, and build at any scale — integrating seamlessly with modern technologies and libraries, while providing a robust command-line interface (CLI), caching, and dependency management. Nx offers developers advanced CLI tools and plugins for modern frameworks, tests, and tools.
For this article, we will be focusing on how Nx works with Next.js applications. Nx provides standard tools for testing and styling in your Next.js applications, such as Cypress, Storybook, and styled-components. Nx facilitates a monorepo for your applications, creating a workspace that can hold the source code and libraries of multiple applications, allowing you to share resources between applications.
Why Use Nx?
Nx provides developers with a reasonable amount of functionality out of the box, including boilerplates for end-to-end (E2E) testing of your application, a styling library, and a monorepo.
Many advantages come with using Nx, and we’ll walk through a few of them in this section.
Web forms are at the center of every meaningful interaction, so they’re worth getting a firm handle on. Meet Adam Silver’s Form Design Patterns, a practical guide to designing and building forms for the web.
Nx for Publishable Libraries
Nx allows you to create publishable libraries. This is essential when you have libraries that you will use outside of the monorepo. In any instance where you are developing organizational UI components with Nx Storybook integration, Nx will create publishable components alongside your stories. The publishable components can compile these components to create a library bundle that you can deploy to an external registry. You would use the
--publishable option when generating the library, unlike
--buildable, which is used to generate libraries that are used only in the monorepo. Nx does not deploy the publishable libraries automatically; you can invoke the build via a command such as
nx build mylib (where
mylib is the name of the library), which will then produce an optimized bundle in the
mylib folder that can be deployed to an external registry.
Nx gives you the option to create a new workspace with Next.js as a preset, or to add Next.js to an existing workspace.
To create a new workspace with Next.js as a preset, you can use the following command:
This command will create a new Nx workspace with a Next.js app named “todo” and with
styled-components as the styling library.
Then, we can add the Next.js application to an existing Nx workspace with the following command:
Building a Next.js and Nx Application
The Nx plugin for Next.js includes tools and executors for running and optimizing a Next.js application. To get started, we need to create a new Nx workspace with
next as a preset:
The code block above will generate a new Nx workspace and the Next.js application. We will get a prompt to use Nx Cloud. For this tutorial, we will select “No”, and then wait for our dependencies to install. Once that’s done, we should have a file tree similar to this:
📂apps folder, we’ll have our Next.js application “todo”, with the preconfigured E2E test for the to-do app. All is this is auto-generated with the powerful Nx CLI tool.
To run our app, use the
npx nx serve todo command. Once you’re done serving the app, you should see the screen below:
Building the API
At this point, we have set up the workspace. Up next is building the CRUD API that we will use on the Next.js application. To do this, we will be using Express; to demonstrate monorepo support, we will build our server as an application in the workspace. First, we have to install the Express plugin for Nx by running this command:
Once that’s done, we are ready to set up our Express app in the workspace provided. To generate an Express app, run the command below:
nx g @nrwl/express:application will generate an Express application to which we can pass additional specification parameters; to specify the name of the application, use the
--name flag; to indicate the front-end application that will be using the Express app, pass the name of an app in our workspace to
--frontendProject. A few other options are available for an Express app. When this is done, we will have an updated file structure in the
apps folder with the
📂todo-api folder added to it.
todo-api folder is an Express boilerplate with a
main.ts entry file.
We will be creating our routes inside this app. To get started, we will initialize an array of objects with two key-value pairs,
id, just under the app declaration.
Next up, we will set up the route to fetch all to-do lists under
The code block above will return the current value of
todoArray. Subsequently, we will have routes for creating, updating, and removing to-do items from the array.
To create a new to-do item, all we need is the value of the new item as a string. We’ll generate an ID by incrementing the ID of the last element in the array on the server. To update an existing item, we would pass in the new value for the item and the ID of the item object to be updated; on the server, we would loop through each item with the
forEach method, and update the item in the place where the ID matches the ID sent with the request. Finally, to remove an item from the array, we’d send the item’s ID to be removed with the request; then, we filter through the array, and return a new array of all items not matching the ID sent with the request, assigning the new array to the
Note: If you look in the Next.js application folder, you should see a
proxy.conf.json file with the configuration below:
This creates a proxy, allowing all API calls to routes matching
/api to target the
Generating Next.js Pages With Nx
In our Next.js application, we will generate a new page,
home, and an item component. Nx provides a CLI tool for us to easily create a page:
Upon running this command, we will get a prompt to select the styling library that we want to use for the page; for this article, we will select
styled-components. Voilà! Our page is created. To create a component, run
npx nx g @nrwl/next:component todo-item; this will create a
component folder with the
API Consumption in Next.js Application
In each to-do item, we will have two buttons, to edit and delete the to-do item. The asynchronous functions performing these actions are passed as props from the home page.
For the updating functionality, we have an input that is disabled when the
isEditingItem state is
false. Once the “Edit” button is clicked, it toggles the
isEditingItem state to
true and displays the “Update” button. Here, the input component is enabled, and the user can enter a new value; when the “Update” button is clicked, it calls the
updateItem function with the parameters passed in, and it toggles
isEditingItem back to
home page component, we have the asynchronous functions performing the CRUD operation.
In the code block above, we have
fetchItems, which returns
todoArray from the server. Then, we have the
createItem function, which takes a string; the parameter is the value of the new to-do item. The
updateItem function takes two parameters, the ID of the item to be updated and the
updatedItem value. And the
deleteItem function removes the item matching the ID that is passed in.
To render the to-do item, we map through the
Our server and front end are now set up. We can serve the API application by running
npx nx serve todo-api, and for the Next.js application, we run
npx nx serve todo. Click the “Continue” button, and you will see a page with the default to-do item displayed.
We now have a working Next.js and Express application working together in one workspace.
Nx has another CLI tool that allows us to view the dependency graph of our application in our terminal run. Run
npx nx dep-graph, and we should see a screen similar to the image below, depicting the dependency graph of our application.
Other CLI Commands for Nx
As a general overview of Nx, this article has covered what Nx offers and how it makes work easier for us. We also walked through setting up a Next.js application in an Nx workspace, adding an Express plugin to an existing workspace, and using the monorepo feature to house more than one application in our workspace.
You will find the complete source code in the GitHub repository. For additional information about Nx, check out the documentation or the Nx documentation for Next.js.
(ks, vf, yk, il, al)
This content was originally published here.