From 845d4ffc5845802e78b542a41c68a94ca700f83a Mon Sep 17 00:00:00 2001 From: Brian Ng Date: Thu, 7 Mar 2019 09:39:45 -0600 Subject: [PATCH] update 7.0.0 doc too --- .../version-7.0.0/plugin-transform-typescript.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/website/versioned_docs/version-7.0.0/plugin-transform-typescript.md b/website/versioned_docs/version-7.0.0/plugin-transform-typescript.md index b8fafb01f1..5032e9f48a 100644 --- a/website/versioned_docs/version-7.0.0/plugin-transform-typescript.md +++ b/website/versioned_docs/version-7.0.0/plugin-transform-typescript.md @@ -9,10 +9,17 @@ Does not type-check its input. For that, you will need to install and set up Typ ## Caveats -* Does not support [`namespace`][namespace]s. **Workaround**: Move to using [file exports][fm], or migrate to using the `module { }` syntax instead. +* Does not support [`namespace`][namespace]s. + + **Workaround**: Move to using [file exports][fm], or migrate to using the `module { }` syntax instead. + * Does not support [`const enum`][const_enum]s because those require type information to compile. -**Workaround**: Remove the `const`, which makes it available at runtime. -* Does not support [`export =`][exin] and [`import =`][exin], because those cannot be compiled to ES.next. **Workaround**: Convert to using `export default` and `export const`, and `import x, {y} from "z"`. + + **Workaround**: Remove the `const`, which makes it available at runtime. + +* Does not support [`export =`][exin] and [`import =`][exin], because those cannot be compiled to ES.next. + + **Workaround**: Convert to using `export default` and `export const`, and `import x, {y} from "z"`. ## Example