From d156afff2e95b450f86bacfcc5c3fd27bf5744aa Mon Sep 17 00:00:00 2001 From: Eduardo Leggiero Date: Sat, 22 Jul 2017 18:19:54 +0100 Subject: [PATCH] Fixed "node: current" example `parseFloat` is not applied anymore to "node: current" logic: The parseFloat was wrong, as `parseFloat('6.3.2')` will parse as 6.3, but `parseFloat('6.10.2')` will output 6.1 that is not correct. Ref: https://github.com/babel/babel-preset-env/blob/master/src/targets-parser.js#L73 --- experimental/babel-preset-env/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/experimental/babel-preset-env/README.md b/experimental/babel-preset-env/README.md index 3d41a28dab..2f3c2b09ae 100644 --- a/experimental/babel-preset-env/README.md +++ b/experimental/babel-preset-env/README.md @@ -112,7 +112,7 @@ The [data](https://github.com/babel/babel-preset-env/blob/master/data/plugins.js `number | string | "current" | true` -If you want to compile against the current node version, you can specify `"node": true` or `"node": "current"`, which would be the same as `"node": parseFloat(process.versions.node)`. +If you want to compile against the current node version, you can specify `"node": true` or `"node": "current"`, which would be the same as `"node": process.versions.node`. ### `targets.browsers`