Conversation
packages restructure
replaced with getDefaultConfig protected method in Pvm class. I dont want to give user ability to override plugins in config when using node api. Config in repo should define pvm behaviour in all cases (cli and node). Envs is exception
* docs: troubleshooting --------- Co-authored-by: Mikhail Shipov <mshipov@yandex.ru> (cherry picked from commit d1385e9)
Он намного информативней в случае монореп. Что превышает возможные неудобства в синглерепе, которых меньшиство по сути (cherry picked from commit 6ed9e28)
default strategy now is list-with-packages
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.