strictMode option should be documented by @babel/plugin-transform-modules-commonjs

Bug Report

Current Behavior There’s no documentation for strictMode and only for strict which doesn’t help remove “use strict”.

Expected behavior/code This should be properly documented.

Babel Configuration (.babelrc, package.json, cli command)

{
    "plugins": [
      "@babel/plugin-syntax-object-rest-spread",
      ["@babel/plugin-transform-modules-commonjs", {
        "strictMode": false
      }]
    ]
  }

Environment

• Babel version(s): 7.0.0-beta.46
• Node/npm version: Node 8/npm 5
• OS: OSX 10.13.1
• Monorepo no
• How you are using Babel: cli, register

Possible Solution

Update Readme file

Additional context/Screenshots

[loganfsmyth]

Because ES module syntax automatically means that a file is strict, and you rely on non-strict features, it would make sense for you to write your module using standard CommonJS, with module.exports and require and such, in my opinion.

If you do that, you can just set sourceType: "script" in your Babel options, and it will skip adding the use strict. Of course, since you’re manually enabling the module transform, you can also just leave that out of your config and you’d be fine too.

[dezman]

I think perhaps strict mode could be disabled by default in development, as I’d like to access arguments.callee ~> Uncaught TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed on strict mode in the console.