将所有 Meteor 包更新到最新版本 [英] Updating all Meteor packages to latest versions

查看:64
本文介绍了将所有 Meteor 包更新到最新版本的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在开发一个尚未投入生产的 Meteor 应用程序,因此我可以在采用新的软件包版本时迅速采取行动(例如,在我集成它几个小时后,用户帐户的版本发生了重大变化.) 这就是我认为 meteor update 应该完成的.然而,当我跑步时:

流星更新

从我的项目中,我被告知包已更新,但 .meteor/versions 保持不变.

我可以通过运行 meteor add someone:package@whatever 来升级包,但这只是将版本依赖从 .meteor/versions 改组到 .meteor/packages 即使它似乎进行了升级.我很高兴在进入生产环境时锁定版本,但似乎在开发中我应该能够使用更新命令,尤其是 meteor list 指示下一步.>

我已经通过删除 .meteor/versions 和 .meteor/local 并运行 meteor update 成功地升级了我的所有软件包,但这看起来很混乱.

我也发现了这个问题,但已关闭.它应该重新打开还是我应该打开一个新问题?我了解 semver 的工作原理,但我认为问题在于 Meteor 没有将其约束求解器结果写入 .meteor/versions,因此没有意识到已应用包更新.这是准确的还是我只是误解了什么?

解决方案

就目前而言,对于包含要使用的更新的软件包,您似乎有 2 个选项:

  1. 通过meteor remove provider:package_namemeteor add provider:package_name
  2. 删除和添加关注的包
  3. 通过meteor add provider:package_name@X.X.X
  4. 手动更新软件包的特定版本

除非您删除并添加软件包,否则 Meteor 不会更新软件包#2500

I'm developing a Meteor app that isn't yet in production, so I can afford to move quickly when adopting new package versions (useraccounts had a significant version bump a few hours after I'd integrated it, for instance.) This was what I thought meteor update was meant to accomplish. Yet when I run:

meteor update

from my project, I'm told that packages were updated but .meteor/versions remains unchanged.

I can upgrade the package by running meteor add someone:package@whatever, but this just shuffles the version dependency from .meteor/versions to .meteor/packages even though it seems to do the upgrade. I'm happy to lock versions down when I go to production, but it seems like in development I should be able to use the update command, especially as meteor list indicates that as a next step.

I've managed to upgrade all my packages by removing .meteor/versions and .meteor/local and running meteor update, but this seems messy.

I also found this issue but it was closed. Should it be reopened or should I open a new issue? I understand how semver works, but I think the issue is that Meteor isn't writing its constraint solver results to .meteor/versions so doesn't realize that package updates have been applied. Is that accurate or am I just misunderstanding something?

解决方案

For the time being it looks like that you have 2 options for packages which have updates you wish to use:

  1. remove and add the package of concern via meteor remove provider:package_name and meteor add provider:package_name
  2. update packages with their specific version manually via meteor add provider:package_name@X.X.X

Meteor won't update packages unless you remove and add them #2500

这篇关于将所有 Meteor 包更新到最新版本的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆