So, finding the main entry isn't as simple as that, although we can make concessions to not be identical to node.

What's implemented in new loader is use manifest's `main` key if it exists (and resolve to relative root so `index.js === ./index.js`), otherwise use `index.js`. Now, what I just realized is not implemented is, if you give a main key like `dir`, it'll first look for `./dir.js`, and then `dir/index.js` (doesn't seem to check for a package.json in a subdir, like it would for a node module lookup). What I'm saying is, is there a way we can use a loader method in AOM? So we can reuse the 'getManifestMain`, which can leverage the 'node style' lookup we already have in the new loader?

Currently v

```js
// Default `main` entry to './index.js' and ensure is relative,
// since node allows 'lib/index.js' without relative `./`
function getManifestMain (manifest) {
  let main = manifest.main || './index.js';
  return isRelative(main) ? main : './' + main;
}
```

+