Use npm as default package manager #152
Merged
Conversation
This file contains 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
Chrico
approved these changes
Aug 21, 2024
tyrann0us
approved these changes
Aug 22, 2024
# Conflicts: # docs/archive-creation.md # docs/assets-compilation.md # docs/build-and-push-assets.md # docs/ddev-playwright.md # docs/js.md # docs/wp-scripts.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Refactor
What is the current behavior? (You can also link to an open issue here)
Yarn is used as the default package manager.
What is the new behavior (if this is a feature change)?
Npm is used as the default package manager. A deprecation warning is displayed for those using the
PACKAGE_MANAGERinput.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
There may be instances where this can cause issues since Yarn and npm are not fully interchangeable.
In such cases, the users can choose to explicitly set the
PACKAGE_MANAGERtoyarn.Other information:
Based on the AT decision.