Jason Miller

I wish I knew more, basically the name lookup fails because it can't figure out what preset module to look under.

For what it's worth, Babel is basically dropping support for npm 2. That that it's a big deal, just i know personally I was a holdout but have finally switched...

It's so much faster, you won't regret it!

For sure!

I don't believe there are tests for it. `getModuleName()` accepts a file path (a package main) and attempts to pluck out the NPM package name from it. Basically the next...

@sorgloomer Needs some extra logic to support namespaced packages. `@foo/bar` - they show up as directories within `node_modules`.

Also, it might be easier to use `path.resolve(pathname)` so we don't have to worry about jumps? For the `split()`, could do: `pathname.split(path.separator)`.

@dshaw @bnb - I don't think I will be able to make it sadly, I'm stuck at the DMV.

I think I will be able to attend remotely, if possible.

We need some form of exception catching in core in order to support componentDidCatch, but perhaps there's a way to make it conditional on the existence of a `componentDidCatch` somewhere...