Robert E. Griffith

Sorry about all the extraneous commits. It took me a while to find 'npm run lint' (I did try a lot of 'apm ..' commands) I would clean it up...

I created a new branch "feature-decorate-disabled-pkg-keymap-clean" that has the same code as this branch (feature-decorate-disabled-pkg-keymap) but only one commit.

### Another anomaly When I use line (1) (old way) to export my instance, the 'this' pointer I see in the constructor is not the one that I see via...

Writing this issue helped me realize that maybe this is about supporting default export and named exports at the same time? Maybe the 'default' member of the proxy is making...

I have this error also in an Atom package (i saw your issue in eslint-plugin-ava #210 too). I wrote an atom plugin and an npm library package that the atom...

FYI, in my library's index.js, I put a guard 'if (!_._global__) require = require("esm")(module)' and it works. It seems that at the npm package boundary, esm does not handle files...

Update, I am putting the if (!_._global__) guard in each of my packages entry point files for the time being as an ugly work-a-round. My best understanding of it so...

update: I now find that one Atom package works fine with the work-a-round of checking to see if __global__ already exists. But if I have two packages that use that...