Currently the officially recommended method for auto-importing works with Babel-like configuration that automatically resolves `dotenv/config` to `dotenv/config.js`. However, Node.js doesn't do this resolution, and instead you have to manually specify the extension like this:

```js
// Babel OK, doesn't work on Node.js
import "dotenv/config";

// Works on Node.js (and Babel etc)
// See #89 (comment)
import "dotenv/config.js";
```

A way of fixing this is by defining the export mapping in `package.json` as [explained in Node.js documentation](https://nodejs.org/api/packages.html#packages_package_entry_points):

```js
  "exports": {
    ".": "./lib/main.js",
    "./config": "./config.js"
  },
```

Fix small typo in JSDoc comment

Allow for `import "dotenv/config";` in Node.js