Handled invalid formatter function props being passed

[Bluebberies]

Problems

1. When the formatter prop is provided as a value that is not a function (e.g., null, undefined, or a non-callable object), the component raises an exception indicating that "formatter is not a function." This results in a stack trace being logged, which exposes the internal error and disrupts the user experience.

2. When a valid function is provided to the formatter prop, if that function throws an error during execution, it leads to an unhandled exception that crashes the application. This prevents the TimeAgo component from rendering as intended, impacting the overall functionality and user interface.

Solutions

1. Implemented a check to determine if the formatter is a function. If it is not, a warning is logged, and the component falls back to using the defaultFormatter. This ensures that the component can still render valid output without crashing.

2. Wrapped the call to the formatter in a try-catch block to catch any errors that may arise during its execution. If an error is thrown, a warning is logged, and the component gracefully falls back to the defaultFormatter.

Ensured all test cases pass

[nmn]

The fix makes sense, but there are some mistakes that need to be fixed.

Thanks!

[nmn]

Suggested change

	const result = formatter(value, unit, suffix, then, nextFormatter, now)
	const nextFormatter = defaultFormatter.bind(null, value, unit, suffix)
	const result = formatter(value, unit, suffix, then, nextFormatter, now)

[nmn]

Suggested change

	const nextFormatter = (value, unit, suffix) => {
	const formatter = (value, unit, suffix) => {

[nmn]

Suggested change

	{nextFormatter(value, unit, suffix)}
	{formatter(value, unit, suffix)}