-
Notifications
You must be signed in to change notification settings - Fork 374
chore: use yarn 3 for development #9201
Conversation
* Cleanup scripts * Fix linux specific issue with `@microsoft/orchestrator-core` not being built * Split `.yarnrc.yml` files for dev and prod, so prod could use Azure registry * Update yarn-berry lockfiles * Remove old yarn lockfiles
b81196a to
e69b334
Compare
e69b334 to
92642cb
Compare
Composer/packages/client/src/recoilModel/dispatchers/provisionQNA.ts
Outdated
Show resolved
Hide resolved
be95dc1 to
b91417f
Compare
537cbd6 to
35f8c11
Compare
tonyanziano
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 minor comments, otherwise it looks good 👍
| import { TokenCredentials } from '@azure/ms-rest-js'; | ||
| import { SearchManagementClient } from '@azure/arm-search'; | ||
| import { SkuName } from '@azure/arm-search/lib/models'; | ||
| import { SkuName } from '@azure/arm-search/esm/models'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just curious: why was this changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I recall yarn 3 resolved packages a bit differently and in the newer package types moved to esm folder
|
Looks like the most recent unit test run failed: Summary of all failing tests |
|
I believe worker died. Let's see if it passes |
Description
@microsoft/orchestrator-corenot being built.yarnrc.ymlfiles for dev and prod, so prod could use Azure registry#minor