Upgrade Rspack and update package.json #12
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
remove some copied unuseful commands
|
New and updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
…e audit high risk
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.
After rspack released version 0.3.14 yesterday, which is more robust and also contained the
./package.jsonin theexportfields (actually this is released in version 0.3.12), which caused the issue 8, now we can publish the new release and package with this version.I also
BTW, do we need to bump the version every time when one PR is merged? I suggest that version 0.0.3 is proper for the new release. What do you think? @th3fallen