I’m almost finished upgrading my Meteor app to 3.0. One thing that is still missing is to re-add montiapm. I read here:
that I would need montiapm:agent@3.0.0-beta.13 for this to work.
However, as soon as I add the package, I get a version conflict:
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint http@3.0.0-alpha300.18||3.0.0 is not satisfied by http 1.4.4.
Constraints on package "http":
* http@1.4.2 <- top level
* http@1.4.0 || 2.0.0 <- meteoreact:accounts 1.2.4_2
* http@1.0.0 || 2.0.0 <- meteortesting:mocha 2.1.0
* http@3.0.0-alpha300.18||3.0.0 <- montiapm:agent 3.0.0-beta.13
I was wondering why Meteor did not update my http package. I can see in a Meteor 3 app I built from scratch, that the package is missing there.
Would updating this to 3.0.0 cause any side-effects? We have some REST endpoints that use WebApp.connectHandlers.use, and I am wondering if these might be affected? I know that I might need to upgrade these anyways, to the new Express syntax.
The HTTP package is for creating http requests, similar to using fetch. Version 3 of it removed fibers from some api’s. If you haven’t had problems so far, it’s possible those packages are not using the parts of the HTTP package that uses fibers.
The agent having a version constraint on the http package has caused this problem for more apps than I had expected. If you update to beta 14, it no longer forces the http package to be version 3.
Thank you so much for your fast response. Will update to beta 14 then.
I am still wondering why Meteor did not touch my existing http 1.4.2 when upgrading to Meteor 3, and why it is not included in a fresh Meteor 3 installation. Is it not needed by Meteor itself anymore?