From a135ab00f6256ee20227fc7a5076203f0a65080c Mon Sep 17 00:00:00 2001 From: Bernhard Reiter Date: Thu, 3 Aug 2017 15:40:00 +0200 Subject: [PATCH 1/3] package.json: Change main to esnext To better denote we're dealing with untranspiled code. See http://2ality.com/2017/06/pkg-esnext.html --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 697d290..31894e9 100644 --- a/package.json +++ b/package.json @@ -2,7 +2,7 @@ "name": "notifications-panel", "version": "1.2.7", "description": "The core notifications panel for WordPress.com notifications", - "main": "src/Notifications.jsx", + "esnext": "src/Notifications.jsx", "scripts": { "build": "webpack", "build:prod": "NODE_ENV=production webpack -p", From 48348a9700d2d6e72f090d70c3332e47c71c6301 Mon Sep 17 00:00:00 2001 From: Dennis Snell Date: Mon, 30 Oct 2017 23:36:29 -0400 Subject: [PATCH 2/3] Version-bump major version because of integration API change We previously used `main` inside of `package.json` to define where to pull in untranspiled code into the project and this change starts using the `esnext` property as seen in http://2ality.com/2017/06/pkg-esnext.html That means (to me at least) that any software which has been using this will have to make changes in order to not break when updating from the previous versions when their build systems looked for the `main` property. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 31894e9..2010ddf 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "notifications-panel", - "version": "1.2.7", + "version": "2.0.0", "description": "The core notifications panel for WordPress.com notifications", "esnext": "src/Notifications.jsx", "scripts": { From 2b926758175250ddc85709bf342bbd5b2bd0bdf9 Mon Sep 17 00:00:00 2001 From: Kirk Wight Date: Thu, 2 Nov 2017 15:43:29 -0700 Subject: [PATCH 3/3] Drop version to a minor version v1.3.0. THis PR has been replicated on the `react16` branch as v2.1.0. This minor version bump will allow either of the two Calypso-related PRs to land first. Related: * https://github.com/Automattic/wp-calypso/pull/16870 * https://github.com/Automattic/wp-calypso/pull/19083 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 2010ddf..d647f38 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "notifications-panel", - "version": "2.0.0", + "version": "1.3.0", "description": "The core notifications panel for WordPress.com notifications", "esnext": "src/Notifications.jsx", "scripts": {