feat: Generator for package move migration#22506
Conversation
📊 Bundle size report🤖 This report was generated against f3c6462af3efa4f8cbe32d289e8e3d4a450b8a3b |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit dfc30e2:
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: f3c6462af3efa4f8cbe32d289e8e3d4a450b8a3b (build) |
|
are the TS path aliases updated during the move ? They are based off path so should break if the packages are moved |
Yup the path aliases are automatically updated |
| // the package name with a new name based on the "destination" flag. This check | ||
| // reverts the changes it makes. | ||
| updateReadMe(tree, schema); | ||
| updateStorybookTypeImport(tree, schema); |
There was a problem hiding this comment.
follow up: we'll need to handle also codeowners file , btw this stuff is DOPE
New Behavior
yarn nx workspace-generator move-packages --name=@fluentui/react-text --destination=test/react-textwill move all contents of the@fluentui/react-textpackage to packages/test/react-text.--allConvergedscope.--allV8scope but the actual migration will actually fail as of now due to the current nature of v8's DX.Demo
Note: generator has been renamed to
move-packagessince recording of video.index.ts.-.v8-buildwork.WSL_.Ubuntu.-.Visual.Studio.Code.2022-04-13.20-45-03.mp4