Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency tsconfig-paths-webpack-plugin to v4.1.0 #2169

Merged
merged 1 commit into from
Jul 17, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 11, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tsconfig-paths-webpack-plugin 4.0.1 -> 4.1.0 age adoption passing confidence

Release Notes

dividab/tsconfig-paths-webpack-plugin (tsconfig-paths-webpack-plugin)

v4.1.0

Compare Source

Added
  • Remove warning on missing baseUrl, which tsconfig-paths ^4.0.0 doesn't require anymore #​105. Thanks to @​sverweij for this PR!

  • Add support for multiple tsconfig paths #​79. Thanks to @​lynch16 for this PR!

Fixed
  • Update tsconfig file name in .npmignore #​100. Thanks to @​tcd for this PR!

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@kamilmysliwiec kamilmysliwiec merged commit 56c7b83 into master Jul 17, 2023
1 check passed
@delete-merged-branch delete-merged-branch bot deleted the renovate/tsconfig-paths-webpack-plugin-4.x branch July 17, 2023 07:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant