Updated so that devtools depends on core, and no dependency on devtools from core. #382
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
This stack of pull requests is managed by Graphite. Learn more about stacking. |
seanspeaks
force-pushed
the
devtool-dependency-from-core
branch
from
ed501ae to
cb1e673
Compare
|
seanspeaks
added
the
release
Graphite App
Merge activity
|
|
🚀 PR was released in |
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.
TL;DR
Updated dependencies across core and devtools packages to align versions and add new required packages.
What changed?
How to test?
npm installWhy make this change?
To maintain consistent dependency versions across packages, remove unused dependencies, and add new required packages for upcoming features. This helps prevent version conflicts and reduces the overall package size by removing unnecessary dependencies.
📦 Published PR as canary version:
2.0.0--canary.382.cb1e673.0✨ Test out this PR locally via:
npm install @friggframework/core@2.0.0--canary.382.cb1e673.0 npm install @friggframework/devtools@2.0.0--canary.382.cb1e673.0 npm install @friggframework/eslint-config@2.0.0--canary.382.cb1e673.0 npm install @friggframework/prettier-config@2.0.0--canary.382.cb1e673.0 npm install @friggframework/serverless-plugin@2.0.0--canary.382.cb1e673.0 npm install @friggframework/test@2.0.0--canary.382.cb1e673.0 npm install @friggframework/ui@2.0.0--canary.382.cb1e673.0 # or yarn add @friggframework/core@2.0.0--canary.382.cb1e673.0 yarn add @friggframework/devtools@2.0.0--canary.382.cb1e673.0 yarn add @friggframework/eslint-config@2.0.0--canary.382.cb1e673.0 yarn add @friggframework/prettier-config@2.0.0--canary.382.cb1e673.0 yarn add @friggframework/serverless-plugin@2.0.0--canary.382.cb1e673.0 yarn add @friggframework/test@2.0.0--canary.382.cb1e673.0 yarn add @friggframework/ui@2.0.0--canary.382.cb1e673.0Version
Published prerelease version:
v2.0.0-next.15Changelog
🐛 Bug Fix
@friggframework/core,@friggframework/devtools@friggframework/core,@friggframework/devtools,@friggframework/eslint-config,@friggframework/prettier-config,@friggframework/serverless-plugin,@friggframework/test,@friggframework/uiAuthors: 1