addPackageToProject() not using yarn

[Turbo87]

the addAddonToProject() and addPackageToProject() blueprint methods are currently not using yarn yet if a yarn.lock file exists. we should probably adjust that.

[RobbieTheWagner]

It looks like from #6790 that we need to do some consolidation here, rather than just simply checking for yarn.lock and using yarn. Do we want to do all that in one fell swoop, or should this still be implemented separately before we consolidate?

[Turbo87]

@rwwagner90 whatever is easier I guess. #6863 should probably be handled first though.

[RobbieTheWagner]

@Turbo87 okay, I can take a stab at these sometime this week, hopefully.

[michielboekhoff]

@rwwagner90 Have you picked this up? Otherwise I might take a crack at it.

[RobbieTheWagner]

@michielboekhoff I haven't yet. Feel free to give it a shot! I won't be able to get to it for a couple days.

[michielboekhoff]

@Turbo87 Could you give me some more info? Right now, it seems like addPackagesToProject and addAddonToProject go through NpmInstallTask, which does use Yarn if a yarn.lock is available. What is the expected behaviour you're after?

[Turbo87]

it seems like addPackagesToProject and addAddonToProject go through NpmInstallTask

@michielboekhoff in that case we can just close the issue. I wasn't sure if that was the case already or not and opened the issue as a reminder to check if it was the case or implement it if necessary. Thanks for figuring it out! 👍