From cb0b9bff02d160d0630fdedbd7587e0ec9fc572a Mon Sep 17 00:00:00 2001 From: "Alexis H. Munsayac" Date: Sun, 19 Nov 2023 11:02:08 +0800 Subject: [PATCH] Update compatibility.md --- docs/compatibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/compatibility.md b/docs/compatibility.md index 86bdaa32..d04aa1ce 100644 --- a/docs/compatibility.md +++ b/docs/compatibility.md @@ -160,7 +160,7 @@ By default, all feature flags are enabled. The following are the feature flags a [^6]: `Feature.ErrorPrototypeStack` must be enabled if serializing `Error.prototype.stack` is desired. [^7]: `Feature.AggregateError` must be enabled, otherwise `AggregateError` is serialized into an `Error` instance. [^8]: `Feature.Symbol` must be enabled, otherwise throws an `UnsupportedTypeError`. -[^9]: `Feature.WebAPI` must be enabled, otherwise throws an `UnsupportedTypeError` (except for `Iterable ` and `AsyncIterable` instances, whereas `Feature.Symbol` must be enabled). +[^9]: `Feature.WebAPI` must be enabled, otherwise throws an `UnsupportedTypeError` (except for `Iterable` and `AsyncIterable` instances, whereas `Feature.Symbol` must be enabled). [^10]: `FormData` is partially supported if it doesn't contain any `Blob` or `File` instances. [^11]: `Feature.Promise` must be enabled, otherwise throws an `UnsupportedTypeError`. [^12]: Due to the nature of `Blob` and `File` being an async type (in that it returns a `Promise`-based serializable data) while having a sync constructor, it cannot be represented in a way that the type is consistent to its original declaration.