-
Notifications
You must be signed in to change notification settings - Fork 374
chore: move plugins folder outside of Composer #4399
Conversation
|
Can someone on windows test this with a clean checkout? |
|
This scares me! There is a big PR involving the azurePublish plugin. Any chance we can let that land before we move all the files around? |
|
@benbrown git should be able to handle the conflict since no source code was changed. |
|
@benbrown if you tell me the branch you are working on I can do a merge locally to see. |
|
|
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.
Some minor comments. I'll defer to how the merging of the azure publish branch goes
|
That branch isn't set to merge until later next week. So we'll merge this when ready and I will manage the conflicts. |
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.
Looks good once merge conflicts are fixed
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.
🚢
* move plugins out of composer directory * add compileExtensions script * update references to old plugins directory * add types dependency back * revert typo * ensure that composer libs are built before extensions * force install when extension needs to compile * use git to determine last modified date * update lockfiles * fix ts error * always yarn install and warn if no build script
Description
Also renames it to extensions.
This will help avoid yarn workspace issues with transient dependencies. Extensions should be considered external/isolated modules.
Task Item
#minor