Replies: 2 comments
This comment was marked as spam.
This comment was marked as spam.
-
Even though you specify https://yarnpkg.com/configuration/yarnrc#enableTransparentWorkspaces |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have monorepo with
libs
andyunona
folders which is included inworkspaces
of rootpackage.json
libs
containprivate
andpublic
libraries.public
libraries are published to our private npm registry.yunona
is our web project built bywebpack
and referencesprivate
libs
viaworkspace:
protocol andpublic
libs
vianpm:
protocol.Now, our
public
libraryerarta
has gone ahead and has version1.14.1
(and published to npm), and I also have updatedpackage.json
of web projectyunona
with this this version, and now what I get afteryarn install
which is quite unexpected, it now uses
workspace
protocol vianpm
?I expected it to still consume this package via npm registry - so I specifically set in package.json of web
yunona
projectCan you explain this behavior, and how can I pin
npm:
protocol for good ?thank you
Beta Was this translation helpful? Give feedback.
All reactions