#NETLIFY YARN WORKSPACES PLUS#

sounds like the current implementation.All node_modules at top level, Next in subdirectory.The following project types have been tested May not be possible: needs more investigation of Nx APIs. Pros: Doesn't need any special work by the user, or any config options.

#NETLIFY YARN WORKSPACES PLUS#

Solution 1, plus special case handling for Nx: try reading details of the workspace from the config.We can check the config to ensure that the user has set the value. Pros: Doesn't require any new config options.✅ Solution 1, but require that Nx users set the distDir to a specific value, which overrides the behaviour where it rewrites it to a parent directory that we can't work out.Allow the user to manually set a Next root and a distDir in the plugin config.Cons: doesn't solve the Nx issue, as the distDir can't be found from the config.Pros: Avoids the issue with next config not being a sibling of the publish dir.Allow the user to manually set a Next root directory.Both of the are the case by default with Nx, which changes distDir on the fly to a directory outside of the site root. It also fails if the distDir can't be found from the. Cons: if the publish dir isn't a sibling of the Next config then this fails.If the user sets the publish dir, we might assume that the is in its parent directory.next, except with Nx, which rewrites it on the fly unless it has been changed by the user to something else, in which case it's left alone. By default this is out, and is where we move the files from distDir. The base dir, which is currently where we assume is, and where we run the build command.The exception is with Nx, which I'll cover more below. In most cases we can find this out from the config at 1. Currently the plugin assumes this is cwd(): i.e. When building a Next site, the build plugin needs to know two things: This is a particular problem for Nx sites, as they have no way of running commands from the app directory. This also doesn't work for monorepos that need commands to be run from the root. The workaround of prepending cd the/site/root before the build command does not currently work for Next sites, because build plugins always run from the base directory, meaning the plugin can't find all the Next files. This is because of the way Netlify handles monorepos.

It either needs to be self-contained, or it needs to be in a yarn workspace. This means that it needs a package.json that installs all dependencies. This includes the functions that we're going to write later that will connect to Fauna.Currently we can only handle monorepos if the Next site root directory (that contains ) can be set as base in the netlify.toml or UI. Now, whenever we make updates to our GitHub repo, it will be automatically deployed on our site. We can go back to our overview, and click on the name that we just created and send it to our site. Netlify says the site is live and Gatsby is built. We check on our deploys, we can see the build logs. You can also choose a custom domain name and set all of that up. In this case, I'm going to name it the same as the Git repo. If we scroll down, we can change the site name. While the site-deploy is in progress, we'll change some of our site settings. We'll run yarn workspace We'll point to packages/www/public and we'll deploy our site. The build command will be run from the root of our project. We need to specify the build command in the publish directory. You can see all of my other projects, such as and. We're going to use Netlify because Netlify supports everything that we need from static site hosting to lambda functions. Chris Biscardi: Now that we've pushed up our Gatsby site, we can deploy it.

Netlify yarn workspaces