Closed CITguy closed 3 years ago
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/hashicorp/structure/ep0y4a9rp
✅ Preview: https://structure-git-build-yarn2-zero-install.hashicorp.vercel.app
Closing. Will submit new PR without the zero-install updates.
Yarn 2 Zero-Install
Updated yarn configuration to make use of Zero-Install capabilities.
In order to remain compatible with logic that expects
node_modules/
to exist, we use thenodeLinker: node-modules
configuration, which still requires runningyarn install
after cloning/pulling to generate files. However, yarn will do so from the local cache (.yarn/cache/*
) instead of pulling from the remote NPM registry.The Numbers
Here's what was observed in Vercel log output.
Vercel Build
Vercel builds were also failing on every other push, because of two items:
yarn install
command has to be run.We can't fix item 1, but I've modified the Vercel configuration to use![vercel - hashicorp - structure - root directory](https://user-images.githubusercontent.com/545605/99706450-b1042d00-2a60-11eb-96d9-4b3e964ea721.png)
packages/pds-ember
as the Root Directory.Additionally, the build settings have been updated to reflect the Root Directory configuration and to reduce log output. Vercel truncates logs to the last 2000 lines, which isn't useful when builds were spitting out a ludicrous amount of unnecessary info.![vercel - hashicorp - structure - build and dev settings](https://user-images.githubusercontent.com/545605/99706710-15bf8780-2a61-11eb-96dc-f7bce28cae06.png)
NOTE: the BUILD COMMAND will be changed to
yarn build:ci
(added in this PR) once the PR is merged.With the configuration changes, builds appear to be finishing successfully, without intermittent errors.