-
-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All monaco-vscode packages are peerDependencies #809
Conversation
@CGNonofr the approach works with npm, pnpm and yarn. I just tested it with the next-14 release. |
is there a list of dependencies we need now to prodivde? |
@cdietrich no, there should be no change on your end needed, but if you have an incompatible monaco-vscode package it will now flag this during install. Depending on the default setting of the package manager the install will fail immediately (npm) or a warning is written (pnpm). |
@CGNonofr if you agree with this I will perform the final release of the packages (finally 😆) later today or tomorrow. |
hmmm
|
@cdietrich this verification example https://github.com/TypeFox/monaco-languageclient/blob/issue-789/verify/peer/package.json will fail with npm |
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.
👍
@cdietrich which package manager? |
we are using yarn. with
yarn will complain about missing peers but at runtime it will fail with e.g.
|
so i added all of these |
@cdietrich yes, yarn needs more (it used to be like that before) it does not automatically install required peers (npm and pnpm do). Had to do the same: https://github.com/TypeFox/monaco-languageclient/blob/main/verify/yarn/package.json Even with latest yarn there is not argument available that allows to install peer dependencies directly. Don't ask me why.🤷♂️ |
@CGNonofr figuring this out was time-consuming (more than I expected). I don't know how many times I installed packages today. |
@CGNonofr one very important thing to note here. The peerDependencies work nicely with released packages available via npm. The enforcement does not work inside a npm workspace. I had a wrong devDependency defined in |
This fixes #789 and is related to CodinGame/monaco-vscode-api#544