![]() Yarn should pick up the package manifests in each subfolder in packages/*. ![]() Now, move all applications into the new folder. The paths are defined in a list inside the workspaces key in the main package.json. It will also create a packages folder, where Yarn will expect the applications to be. This will generate a root-level package.json. Next, initialize the monorepo workspaces. Start by ensuring that you’re running the latest Yarn version. The first thing to do is set up the workspaces. web: a Next.js static website generated programmatically with the API.īoth of them ship with linting checks and unit tests, plus some integration tests to confirm that they can work together.api: provides a GraphQL API server that returns information about countries and cities of the world.The example repository contains two applications: The steps laid down here, however, should mostly work with any JavaScript application. You can peek at the final form in the final branch. ![]() We’re going to use one example repository as a guide. Instead of having several big node_modules folders scattered all over, we now have all dependencies compressed in one repository-level folder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |