●Change8

v1.8.0

Breaking Changes
📦 axiosView on GitHub →
⚠ 4 breaking✨ 1 features🐛 3 fixes🔧 4 symbols

Summary

This release adds a new `allowAbsoluteUrls` config for URL handling, updates utils to use the crypto module, and includes several bug fixes, but introduces breaking changes to how URLs are combined.

⚠️ Breaking Changes

  • URL handling logic changed: code that previously preferred the request URL now combines the base URL and request URL; update code or set the new `allowAbsoluteUrls` config to false to retain prior behavior.
  • Introduced `allowAbsoluteUrls` config option which alters how absolute URLs are processed; existing code may need to explicitly set this option to match previous expectations.
  • Added a default value for `allowAbsoluteUrls` in the `buildFullPath` function, potentially affecting custom overrides of this function.
  • Fixed a typo in the flow‑control logic when setting `allowAbsoluteUrls`, which may change the execution path for URL handling.

Migration Steps

  1. Review any code that relied on the previous URL combination behavior and set the `allowAbsoluteUrls` config accordingly.
  2. If you have custom overrides of `buildFullPath`, ensure they handle the new default value for `allowAbsoluteUrls`.
  3. Replace direct calls to `utils.getRandomValues` with the new `crypto`‑based implementation if your code accessed it directly.
  4. Remove or adjust imports of the reverted `fromDataToStream` export, as it is no longer exposed.

✨ New Features

  • Added a configuration option (`allowAbsoluteUrls`) to control whether absolute URLs are ignored or allowed (see #5902, #6192).

🐛 Bug Fixes

  • Fixed crash in the examples application when navigating examples in the browser (see #5938).
  • Corrected a missing word in `SUPPORT_QUESTION.yml` (see #6757).
  • Replaced usage of `getRandomValues` with Node's `crypto` module in utils (see #6788).

🔧 Affected Symbols

buildFullPathallowAbsoluteUrlsutils.getRandomValuesfromDataToStream