package.json: Change main to esnext

[ockham]

To better denote we're dealing with untranspiled code.

Companion Calypso PR: Automattic/wp-calypso#16870

To provide a bit of an explanation -- esnext is a custom field.

• We'll specify it as a possible entry point for webpack to watch out for here.
• OTOH, we use it (as opposed to main) as a flag to indicate that this is a package's entrypoint for untranspiled code here.

This is a strategy found at http://2ality.com/2017/06/pkg-esnext.html.

Suggested order:

• Merge this
• Release new version
• Calypso: Include notifications-panel version bump with Framework: Transpile untranspiled node_modules wp-calypso#16870
• Test Framework: Transpile untranspiled node_modules wp-calypso#16870
• Merge Framework: Transpile untranspiled node_modules wp-calypso#16870

[dmsnell]

this is probably worth a major version bump, no? since software already using this would have to update in order not to break?

[dmsnell]

@gwwar @kwight I have updated this with a major version bump (see the commit description).

Could you two consider this change and indicate if you have any hesitation or questions? This is a change to help @ockham improve Calypso's build process by automatically inferring which node_modules can be included as-is without having to import the already-transpiled builds (which would end up speeding up our build and saving on build-size).

[dmsnell]

Pending review from others

[kwight]

@ockham do you have a strict timeline for this? We've moved to scheduled releases for notifications-panel (p3fqKv-5V6-p2), so this could be part of the next beta on Nov 8th, with production release Nov 22nd; would that work for you?

[gwwar]

To add to that Calypso gets the beta release so unless it's really urgent, it'd be slated for Nov 8.

[ockham]

No strict/urgent timeline, but would totally appreciate this being merged!

[gwwar]

Thanks @ockham we'll try to test/merge this soon, though for now we'll stick with the Nov 8 version bump.

[kwight]

I've committed these changes both to master (by merging this PR with a minor bump to 1.3.0) and to the react16 branch (with a bump to 2.1.0) in 011fc14.

[ockham]

D'oh, this won't work until we merge Automattic/wp-calypso#19698

Quoting Automattic/wp-calypso#19723 (comment):

To fix, we can:

• either merge #19698
• or change back esnext to module in https://github.com/Automattic/notifications-panel
• or add a build step, publish that to npm, and set main to point to the dir that holds the transpiled code