Meteor 如何在新建项目后更新所有间接依赖项

所以，自从meteor将包版本取消固定到发行版后，我就一直遇到这个问题

当我运行

$meteor create[project]

时，将cd放入该项目中，然后使用

$meteor update

我得到以下信息：

$ meteor update
This project is already at Meteor 1.4.0.1, the latest release.
Your top-level dependencies are at their latest compatible versions.

Newer versions of the following indirect dependencies are available:
 * autoupdate 1.2.11 (1.3.11 is available)    
 * caching-compiler 1.0.6 (1.1.6 is available)
 * ddp-client 1.2.9 (1.3.0 is available)      
 * ddp-server 1.2.10 (1.3.9 is available)     
 * http 1.1.8 (1.2.8 is available)            
 * templating 1.1.14 (1.2.13 is available)    
To update one or more of these packages, pass their names to `meteor
update`.

这意味着下一个命令不可避免地是：

$ meteor update autoupdate caching-compiler ddp-client ddp-server http templating

Changes to your project's package version selections from updating package
versions:

autoupdate        upgraded from 1.2.11 to 1.3.11
caching-compiler  upgraded from 1.0.6 to 1.1.6
ddp-client        upgraded from 1.2.9 to 1.3.0
ddp-server        upgraded from 1.2.10 to 1.3.9
http              upgraded from 1.1.8 to 1.2.8
templating        upgraded from 1.1.14 to 1.2.13

坦白说，这很烦人

当我创建一个新项目时，我希望一切都是最新的、最棒的。现在，我明白有时候有些人不想这样，我也同意。但是对于像我这样的人来说，如果有一个meteor更新一切的命令肯定会很好-want爸爸是一辆全新的汽车

有人知道这样的命令吗？接缝不需要列出此命令

---

编辑： 请注意，这也不起作用：

$ meteor update --packages-only
Your top-level dependencies are at their latest compatible versions.

Newer versions of the following indirect dependencies are available:
 * autoupdate 1.2.11 (1.3.11 is available)    
 * caching-compiler 1.0.6 (1.1.6 is available)
 * ddp-client 1.2.9 (1.3.0 is available)      
 * ddp-server 1.2.10 (1.3.9 is available)     
 * http 1.1.8 (1.2.8 is available)            
 * templating 1.1.14 (1.2.13 is available)    
To update one or more of these packages, pass their names to `meteor
update`.