Use `require` instead of `import`

I just started to use flow-runtime & babel-plugin-flow-runtime, because these are very powerful packages.

This is a:

• Bug Report
• Feature Request
• Question
• Other

Which concerns:

• flow-runtime
• babel-plugin-flow-runtime
• flow-runtime-validators
• flow-runtime-mobx
• flow-config-parser
• The documentation website

---

What is the current behaviour?

Currently babel-plugin-flow-runtime generates code like this:

import t from 'flow-runtime';
const User = t.type('User', t.object(
  t.property('id', t.number()),
  t.property('name', t.string())
));

---

What is the expected behaviour?

My proposal is generating code like this:

const t = require('flow-runtime');
const User = t.type('User', t.object(
  t.property('id', t.number()),
  t.property('name', t.string())
));

If I can use flow-runtime & babel-plugin-flow-runtime without adding another plugin to transpile import, it becomes non-intrusive.

---

Which package versions are you using?

---

IssueHunt Summary

Backers (Total: $40.00)

• issuehunt ($40.00)

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

---

IssueHunt has been backed by the following sponsors. Become a sponsor

[jedwards1211]

I would say an option to choose between import and require is best. There are also cases where one would prefer to output import statements (e.g. for webpack)

[bu7ch]

@tnayuki you can : Save files with ES6 modules with .mjs extension and run it like: node --experimental-modules my-app.mjs