From d3a4a7b81a9c68d53e3bbcafa43f3bea3da19560 Mon Sep 17 00:00:00 2001 From: Ray Schamp Date: Thu, 1 Jun 2017 12:31:24 -0400 Subject: [PATCH] Pin to `latest` for 3.0 modules Reverts #551 Pinning to `^0.1.0.prerelease.0` is not equivalent to `latest`, since has the effect of not installing the latest version on `npm install`, you have to also do `npm update`. This hurts us ergonomically on `npm install`, and doesn't help us since we already are releasing breaking changes on `prerelease`. --- package.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/package.json b/package.json index 7314b7b86..ff1f895fe 100644 --- a/package.json +++ b/package.json @@ -42,9 +42,9 @@ "lodash.defaultsdeep": "4.6.0", "minilog": "3.1.0", "promise": "7.1.1", - "scratch-audio": "^0.1.0-prerelease.0", - "scratch-blocks": "^0.1.0-prerelease.0", - "scratch-render": "^0.1.0-prerelease.0", + "scratch-audio": "latest", + "scratch-blocks": "latest", + "scratch-render": "latest", "scratch-storage": "^0.1.0", "script-loader": "0.7.0", "socket.io-client": "1.7.3",