Supporting the "module" package.json property

[guybedford]

The way this proposal handles the "default" could work just as well for the "module" property already in use in the ecosystem by users.

Previously my attempts to work with the "module" property failed (like the In Defense of JS proposal) because it was treating the module property as a package-level flag.

Rather the way this proposal works, would work naturally with the way users already use the "module" property.

Would you be open to a PR to add the adjustment here?

[guybedford]

(basically working like the "default" property in the package.json file mentioned here - #6 (comment))

[zenparsing]

Yes, feel free to make a PR and we can discuss any details there.