Module build error when importing runtime code outside the runtime directory

[cjpearson]

We first noticed this issue when updating from 0.6.0 to 0.7.1.

If you are importing a function from the runtime directory into module.ts, it will fail if the full path to the file includes a period in the path. For example, in my case: /Users/connor.pearson/projects/my-module The directory with the period is parsed as the file instead of the actual file.

Sample reproduction: https://github.com/cjpearson/nuxt-module-builder-filename-issue

To run: yarn && yarn dev:prepare && yarn nuxt-module-build build

ERROR  Cannot find module /Users/connor.pearson/Downloads/filename-test/dist/runtime/utils/connor imported from file:///Users/connor.pearson/Downloads/filename-test, file:///Users/connor.pearson/Downloads/, file:///Users/connor.pearson/Downloads/filename-test/_index.js, file:///Users/connor.pearson/Downloads/node_modules

The project directory or one of its ancestors should include a "." in the path.

I've added an upstream issue here, but maybe this could be fixed by using basename here instead?