Closed jaysoo closed 2 months ago
⚠️ Important: This organization may reach the limit of the FREE Plan and could be disabled at the end of the month. If this happens, remote caching and distributed task execution will no longer work. Your CI may stop working.
CI is running/has finished running commands for commit 9968cdc77052aa32192940c1a657a22d620754e2. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this CI Pipeline Execution
Sent with 💌 from NxCloud.
Netlify deployments currently has two problems:
npx nx-ignore
.For Nx plugins that infer targets from config files, we should do a full installation to ensure packages used by config files are present. Otherwise errors like missing
@playwright/test
ornext/constants
will occur. On Vercel, this works fine because there isn't a limit to the ignore script (at least it is reasonable long). On Netlify, the three minute limit for ignore script means full installation will almost always fail.The fix for this issue is to detect whether we're on Netlify or not (checking
NETLIFY
env var). If we're on Netlify, then perform a slim installation. And to make it more compatible with Project Crystal, we will install known packages that are used in config files (if they are in the rootpackage.json
). Users can also manually pass--additional-packages
option if we miss a package.Note: On the ocean repo,
nx-ignore
goes from 145s to 23s on my local machine.