Please sign in to comment.
Handle more errors in ensureDevBundleLink.
If a developer tried to `meteor update` a project whose `.meteor/release` file corresponded to a version of `meteor-tool` that no longer exists in `~/.meteor/packages/meteor-tool`, this code would throw an ENOENT error. This could be fixed by running `meteor update --release <old release>` first, but that kind of workaround shouldn't be necessary when updating Meteor to the latest version.
- Loading branch information...