chore: bump query-string to ^8.1.0 and update jest config #2319
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.
[中文版模板 / Chinese template]
🤔 This is a ...
query-string
dependency to latest version: 8.1.0 and fix test issues🔗 Related issue link
close: #2155
💡 Background and solution
Upgrade query-string
As the issue above revealed, the⚠️ This has an impact on build assets, maybe a breaking change? 🤔️
?.
operator syntax inquery-string
and its related deps should be transformed. Without introducing additional deps, likebabel-loader
, there is a workaround as webpack/webpack#10227 mentioned, just upgradeWebpack
to version 5 could fix it.Update jest config
Since the latest
query-string
only provide ESM, so it should be transformed by jest. And there is a problem with the current configuration, according to thets-jest
docs, should set allowJs to true intsconfig.json
file when preset set tots-jest/presets/js-with-ts
. It works same as this PR: #1816, but more resonable.Also bump
ts-jest
to latest version to support TypeScript 5.x, and suppress warnings.📝 Changelog
☑️ Self Check before Merge