With the yarn 4.x update that is being tested, I did change the linkType
. Would you be able to test if this fixes your issues?
Can this be confirmed as still an issue?
I know that this is old, if you are still around and want to help get portal:
added also, I would like to understand the use-case better. Would packing the portaled dependency be valid? If so this should not be all that hard to do, however if not I have no clue where to start with this as if the portal is kept where it is on disk it brakes a lot of the assumptions the plugin has around making the workspace's out dir path independent from everything else in the project.
Hi I have worked on an update for yarn 4.x. If anyone would like to try it out you can run this.
yarn plugin import https://gitlab.com/Larry1123/yarn-contrib/-/raw/yarn-4.x-next/packages/plugin-production-install/bundles/@yarnpkg/plugin-production-install.js
Let me know if there are any issues, I have tried to also address a few request and problems others have ran into.
Hello. Thanks for having taken the time to work on this. There are a few things that would need to be cleaned up or changed however I had started working on updating for yarn 4.x on my own without having seen that this was here until I was most of the way done.
I am still testing it out and I also included some things I had been working on from before this also. You can take a look at it here, it should be working. https://gitlab.com/Larry1123/yarn-contrib/-/tree/yarn-4.x-next?ref_type=heads
I'll leave this open for now at least until I merge my yarn 4.x changes into main.
Larry1123 (b5820fa7) at 01 Mar 13:22
document injectCjsPnp feature
Larry1123 (de6657d9) at 01 Mar 13:12
Should be working with yarn 4.x now
Larry1123 (897e2246) at 29 Feb 14:04
Error: @yarnpkg/core@4.0.3 isn't supported by any available resolver
Can you tell me the behavior when you build using yarn pack
because it uses the logic from the pack plugin to get the list of files it needs to copy into the out dir.