开发中的babel-node vs babel-register [英] babel-node vs babel-register in development

查看:84
本文介绍了开发中的babel-node vs babel-register的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在开发中运行代码时,使用babel-register或babel-node 有什么区别吗??这两个选项是:

Is there any difference between using babel-register or babel-node when running my code in development? The two options are:

  1. require('babel-register')({预设":["es2015"]}); 在entry-point.js和npm上启动脚本 node entry entry-point.js

  1. require('babel-register')({ "presets": ["es2015"] }); at entry-point.js and npm start script node entry-point.js

仅具有npm启动脚本 babel-node entry-point.js --preset = es2015

simply have npm start script babel-node entry-point.js --preset=es2015

他们是否做同样的事情?并推荐一种方法吗?

Do they do the exact same thing? And is one way recommended over the other?

推荐答案

我在工作中四处询问并得到了答案.如果有人有兴趣,我将在这里发布.

I asked around at work and got an answer. I'm going to post it here in case anyone else is interested.

babel-node 基本上在内部调用 babel-register .参见.差异是

babel-node basically calls babel-register internally. see source. The differences are

  1. 使用 babel-node 时,入口点本身也将通过babel与 babel-register 运行,仅在 babel-register之后需要文件是必需的,将通过babel运行.

  1. when using babel-node the entry-point itself will also run through babel vs. babel-register only files required after babel-register is required will be run through babel.

如果需要 babel-polyfill (例如生成器), babel-node 会自动将其拉入,而 babel-register ,您需要自己执行此操作.在进行生产生产时要牢记这一点.如果您需要 babel-polyfill ,并且在开发中使用 babel-node ,则需要确保您正在使用 babel-polyfill 进行构建代码>在进行生产时.

if you need babel-polyfill (for eg. generators) babel-node will pull it in automatically, vs. babel-register you'd need to do that yourself. This is something to keep in mind when building for production. If you need babel-polyfill and you are using babel-node in development, you'd need to make sure you are building w/ babel-polyfill when building for production.

似乎没有推荐一种方法优于另一种方法.但是, babel-node 稍微更清洁一点,它将把 require('babel-register')保留在代码库之外.对于刚接触所有这些东西的人来说,这似乎也更直观一些.

One way doesn't seem to be recommended over the other. However, babel-node is a little cleaner b/c it'll keep the require ('babel-register') out of the codebase. It also seems to be a bit more intuitive to someone new to all this stuff.

这篇关于开发中的babel-node vs babel-register的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆