The netlify site name is įull build log: 5:06:27 PM: Build ready to startĥ:06:30 PM: build-image version: ac716c5be7f79fe384a0f3759e8ef612cb821a37 (xenial)ĥ:06:30 PM: buildbot version: 515e5c33287d8b909c004fcf2e460e8645e8c1c6ĥ:06:33 PM: Finished downloading cache in 2.744713793sĥ:06:39 PM: Finished extracting cache in 6.643158425sĥ:06:39 PM: Finished fetching cache in 9.424005841sĥ:06:39 PM: Starting to prepare the repo for buildĥ:06:40 PM: Preparing Git Reference pull/416/headĥ:06:41 PM: Parsing package.json dependenciesĥ:06:42 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'app.website/.next' versus '.next' in the Netlify UIĥ:06:42 PM: Different functions path detected, going to use the one specified in the Netlify configuration file: 'app.website/app.website/out_functions' versus 'app.website/out_functions' in the Netlify UIĥ:06:43 PM: Started restoring cached node versionĥ:06:45 PM: Finished restoring cached node versionĥ:06:45 PM: Attempting node version 'v16' from. But for obvious reasons we don’t want to have to select this every time. **Important: ** clear cache and retry deploying always works. As you can see in the build log below, the build command fails because the next package was not installed. We suspect that it is looking at the cache but not finding our dependencies which are located at the root of the repo and not within the package. The only issue is that with every new commit, the preview build fails as it is not installing the correct dependencies. Me and my team have been trying to get set up NPM workspaces within Netlify and have partially managed to do so.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |