From fb72449fe20b34da6df7d97c7fec8b7f575ab454 Mon Sep 17 00:00:00 2001 From: Tarjei Huse Date: Wed, 11 Dec 2019 09:58:45 +0100 Subject: [PATCH] Add note about the conflict with useBuiltins Hi, this is a stab at #10121. As I understand it, preset-env with useBuiltins set to `usage` conflicts with using the runtime helper, though it is not totally clear to me how. --- docs/plugin-transform-runtime.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/plugin-transform-runtime.md b/docs/plugin-transform-runtime.md index e01d98dcaa..1036b3ea46 100644 --- a/docs/plugin-transform-runtime.md +++ b/docs/plugin-transform-runtime.md @@ -8,6 +8,8 @@ A plugin that enables the re-use of Babel's injected helper code to save on code > NOTE: Instance methods such as `"foobar".includes("foo")` will only work with `core-js@3`. If you need to polyfill them, you can directly import `"core-js"` or use `@babel/preset-env`'s `useBuiltIns` option. +> NOTE: You must choose between using `@babel/preset-env`'s `useBuiltIns` option with `usage` and this plugin. They do not work together. + ## Installation Install it as development dependency.