👷 Other strategy to handle test app lockfiles with renovate#4028
👷 Other strategy to handle test app lockfiles with renovate#4028
Conversation
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage 🔗 Commit SHA: e1e9ff8 | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
4e8dab0 to
776b35f
Compare
Bundles Sizes Evolution
🚀 CPU Performance
🧠 Memory Performance
|
776b35f to
5447b14
Compare
5447b14 to
0bccecf
Compare
| "peerDependenciesMeta": { | ||
| "@datadog/browser-logs": { | ||
| "optional": true | ||
| }, | ||
| "@datadog/browser-rum": { | ||
| "optional": true | ||
| } |
There was a problem hiding this comment.
🥜 nitpick: If we're gonna install them anyway, then they are no optional (and it seems that npm would actually install them automatically, unfortunately this is not the case for yarn)
You might need to add the peer dependencies before doing yarn install in the build script though. I don't know if it's worth it.
There was a problem hiding this comment.
The issue is that renovate don't allow to build those dependencies before running the install to re-generate the lock file.
So the idea is to have a way to run the install without having those dependencies built, otherwise the install fails as the dependencies are missing.
But we still need to build them before effectively be able to use the test apps.
Do you have a simpler alternative in mind?
There was a problem hiding this comment.
all good then! thanks
| printLog(`Building app at ${appPath}...`) | ||
| command`yarn install --no-immutable`.withCurrentWorkingDirectory(appPath).run() | ||
|
|
||
| // install peer dependencies if any |
There was a problem hiding this comment.
💬 suggestion: Maybe add a comment explaining why we are using peed dependencies instead of dependencies. I think I got it but it's not obvious. (ideally that comment would be in the package.json, but 🤷)
| interruptible: true | ||
| script: | ||
| - yarn | ||
| - yarn build |
There was a problem hiding this comment.
💭 thought: I guess this is because otherwise the type definitions from the peer dependencies are not found? That's a bit annoying to have to build just to typecheck 😞 (but I don't see an alternative)
There was a problem hiding this comment.
FYI, here I'm just reverting to the behavior that we add before #4019, since we don't nee to run yarn build at install anymore
Motivation
Previous strategy #4019, #4021, #4023 did not work
Changes
Test instructions
Checklist