#346 fixed an issue where npm wouldn't even install. This fixes the incomplete work begun in #339, making the naming behave as I intended it to.

The algorithm is similar to the last one in that it begins with the directory that the project is in. Because most directories are the same as the repo name, this is fine, I think.

From there, four values need to be generated:

1. the npm module name
2. the file names
3. the repo name
4. the main variable name

The npm module name is a lowercased version of the directory without a .js extension. Here are a few examples:

hello-there.js => hello-there
hello-there => hello-there
react.native-thing.js => react.native-thing
WhatTheModule => whatthemodule

The file names follow the same algorithm as above, but with the extension. So...

hello-there.js => hello-there.js
hello-there => hello-there.js
react.native-thing.js => react.native-thing.js
WhatTheModule => whatthemodule.js

The repo is just the dirname directly (assuming the user used the default value).

And the variable name is the module name in camel case format.

Of course, all of these can be overridden in a straightforward way. This just updates the defaults to be a bit smarter.