Upgrade examples to Meteor 3.6-beta.0 and Rspack 2 - #50
Open
nachocodoner wants to merge 1 commit into
Open
Conversation
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 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.
Summary
Upgrades the following examples from Meteor 3.5.2 to Meteor 3.6-beta.0:
The Rspack integration is migrated through the normal startup path. After the Meteor release update, running each application refreshes the project-level Rspack dependencies to
@rspack/core2.2.0,@rspack/cli2.2.0, and@meteorjs/rspack3.0.0-beta.1. No separatemeteor update --npmstep is required.Compatibility updates
@lingui/swc-pluginto a release compatible with the SWC runtime used by Rspack 2.Validation
meteor update --release 3.6-beta.0in each example.meteor run.Excluded
NFT Marketplace is intentionally unchanged and out of scope for this PR.