{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":661858239,"defaultBranch":"master","name":"example-repo-zip0","ownerLogin":"yarnpkg","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2023-07-03T20:23:43.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/22247014?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1688419613.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"f4e339e0197c538b0a32e61755f87d92416d749b","ref":"refs/heads/master","pushedAt":"2023-07-03T21:26:53.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Exposes packages to constraints (#5555)\n\n**What's the problem this PR addresses?**\r\n\r\nConstraints can only operate on the workspaces' listed dependencies, but\r\nhave no idea about the shape of the global dependency tree. In general\r\nit's enough, but I wanted to write a constraint autofixing missing peer\r\ndependencies, and this wasn't possible without knowing the dependencies\r\nof our dependencies.\r\n\r\n**How did you fix it?**\r\n\r\nI added a concept of \"package\" to the constraint API. Some of their\r\ncharacteristics:\r\n\r\n- They are based on the resolved dependency tree; as a result, there is\r\nno direct concept of devDependency / dependency (just like in the core\r\n`Package` type).\r\n\r\n- They somewhat look like the `Package` type, but with fewer information\r\n(just the dependencies & peer dependencies, at the moment), and with a\r\nslightly different format (no need for serialization, so it directly\r\nreferences other data structure rather than go through string hashes).\r\n\r\n- They don't provide any autofix (or even reporting) capability at the\r\nmoment. Perhaps later I'll add an `error` API, like regular\r\ndependencies, but that'll probably require to enhance them so they are\r\nable to access the packages' filesystems, so it'll have to be a\r\nfollow-up.\r\n\r\nTesting is currently lacking ... like the rest of the JS constraints\r\nengine 😶‍🌫️\r\n\r\n**Checklist**\r\n<!--- Don't worry if you miss something, chores are automatically\r\ntested. -->\r\n<!--- This checklist exists to help you remember doing the chores when\r\nyou submit a PR. -->\r\n<!--- Put an `x` in all the boxes that apply. -->\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n\r\n<!-- See\r\nhttps://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released\r\nfor more details. -->\r\n<!-- Check with `yarn version check` and fix with `yarn version check\r\n-i` -->\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n\r\n<!-- The \"Testing chores\" workflow validates that your PR follows our\r\nguidelines. -->\r\n<!-- If it doesn't pass, click on it to see details as to what your PR\r\nmight be missing. -->\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.","shortMessageHtmlLink":"Exposes packages to constraints (#5555)"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADTgCOagA","startCursor":null,"endCursor":null}},"title":"Activity · yarnpkg/example-repo-zip0"}