From 9723b744a2c7b0c12809a0eaa234dab04f50aca7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABl=20Nison?= Date: Sat, 31 Aug 2019 16:36:06 +0200 Subject: [PATCH] Update plugin-transform-runtime.md --- docs/plugin-transform-runtime.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/plugin-transform-runtime.md b/docs/plugin-transform-runtime.md index 6509fceac4..0af8df09c9 100644 --- a/docs/plugin-transform-runtime.md +++ b/docs/plugin-transform-runtime.md @@ -168,6 +168,12 @@ This allows users to run `transform-runtime` broadly across a whole project. By Using absolute paths is not desirable if files are compiled for use at a later time, but in contexts where a file is compiled and then immediately consumed, they can be quite helpful. +### `relativeRuntime` + +`boolean` or `string`, defaults to `false`. + +Similar to `absoluteRuntime`, but the generated path will be the relative difference between the resolved runtime and the location of the transpiled file. Using this option makes it portable across systems, although it also makes the setup slightly harder as you need to ensure that the relative location of the runtime compared to your sources is the same as the transpiled files. + > You can read more about configuring plugin options [here](https://babeljs.io/docs/en/plugins#plugin-options) ## Technical details