refactor: improve logFn types

[kricsleo]

resolves #351

Since logObj.date must be of type Date, we should enforce stricter parameter types to prevent runtime errors.
In addition to formatDate requiring the Date type, we also use the Date internally:

consola/src/consola.ts

Lines 418 to 422 in 5ac9ed7

	const diffTime =
	this._lastLog.time && logObj.date
	? logObj.date.getTime() - this._lastLog.time.getTime()
	: 0;
	this._lastLog.time = logObj.date;

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.30%. Comparing base (24c98ce) to head (e9268d0).
Report is 57 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #372       +/-   ##
===========================================
- Coverage   61.08%   29.30%   -31.78%     
===========================================
  Files          13       43       +30     
  Lines        1380     1723      +343     
  Branches       58       87       +29     
===========================================
- Hits          843      505      -338     
- Misses        537     1192      +655     
- Partials        0       26       +26     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pi0]

Thanks for PR but it seems type only getting stricter we need to fix runtime support somehow to not wrongly detect { date } as logobj.

[kricsleo]

Do you mean a stricter isLogObj function check, requiring date to be Date if it exists?

consola/src/utils/log.ts

Lines 16 to 33 in 5ac9ed7

	export function isLogObj(arg: any) {
	// Should be plain object
	if (!isPlainObject(arg)) {
	return false;
	}
	// Should contains either 'message' or 'args' field
	if (!arg.message && !arg.args) {
	return false;
	}
	// Handle non-standard error objects
	if (arg.stack) {
	return false;
	}
	return true;
	}

[pi0]

Yes exactly! (types couldbe lean as is IMO. feel free to make another PR for runtime fix)

[kricsleo]

#379 makes the runtime check more strict.

Personally, I prefer stricter types that align with runtime behavior. This can improve DX 😃

(I've also simplified the LogParam<T> for better understanding and easier maintenance)