fix: capture async stack only for rejections with native error object…

[MitchLewis930]

PR_025

[Copilot]

Pull request overview

This PR fixes a bug where async stack traces were being incorrectly captured for non-Error rejections. The fix ensures stack trace augmentation only occurs when the rejected value is an instance of the native Error object.

Changes:

• Modified the stack trace capture logic to only apply to Error instances
• Refactored test case to use async/await pattern instead of callbacks
• Added safety checks for stack property existence

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
lib/core/Axios.js	Added instanceof Error check to conditionally capture and augment stack traces only for Error objects
test/unit/adapters/http.js	Converted callback-based test to async/await pattern using startHTTPServer helper

[Copilot]

The ternary operator assigns different types to dummy (object vs Error instance). This inconsistency could cause issues when accessing properties. Consider using dummy = {}; Error.captureStackTrace ? Error.captureStackTrace(dummy) : (dummy.stack = new Error().stack); to keep dummy consistently as a plain object.

Suggested change

	let dummy;
	Error.captureStackTrace ? Error.captureStackTrace(dummy = {}) : (dummy = new Error());
	let dummy = {};
	if (Error.captureStackTrace) {
	Error.captureStackTrace(dummy);
	} else {
	dummy.stack = (new Error()).stack;
	}