Hello, I get several errors like these trying to update from 2.16 to 3.0:
=> Errors while initializing project:
While selecting package versions:
error: Conflict: Constraint meteor@1.9.2 is not satisfied by meteor 2.0.2.
Constraints on package "meteor":
* meteor@~2.0.0 <- top level
...
Conflict: Constraint caching-compiler@1.2.0 is not satisfied by caching-compiler 2.0.1.
Constraints on package "caching-compiler":
* caching-compiler@~2.0.0 <- top level
* caching-compiler@1.2.0 <- less 2.8.0
...
Conflict: Constraint webapp@1.0.2 is not satisfied by webapp 2.0.3.
Constraints on package "webapp":
* webapp@~2.0.0 <- top level
...
Some of yours meteor packages is not compatible with meteor 3. Try to uninstall meteor packages (except those mostly used), then upgrade meteor and then install packages back. Then you will find those, which are incompatible (which you need to solve it). There is still lot of packages, which are not compatible with meteor 3.
The best way to update your app from version 2.x to 3.x is remove most of the meteor packages, update the Meteor to version 3, and after that you will start to add package by package.
You can have some scenarios:
Some packages have a beta version compatible with Meteor 3 and some times you need to force that version. Ex: meteor add package@x.x.x
Some packages are out dated, so you can try to find some fork up to dated, or update it by yourself.
Probably you will use some time to fix every thing.
…problem is, that lot of packages are still not in beta or deprecated. Therefore upgrade can make some ‘headache’. Also lot of typescripts are also not updated.
Open source works with mutual effort. You need something, you update it an push it back to where it came from. Without this, open source cannot exist.
So, technically that is not a problem. It is a paradigm.
…yes, it’s truth. But on the other side, for Meteor newbies can be problem, when they are waiting for updates (related plugins) …looong time and by self they are not able to update it by self (it’s hard for them).
In this case I suggest people label themselves as newbies and pay the people who label themselves otherwise, to maintain the packages in due time for them.
@paulishca …with paying, it’s always problem. I’m watching lot of another frameworks and it is always problem with setup payment rules, which are working.
I started to help the packages exactly when I needed them to be updated. Most of small packages just need small adjustments. The big packages usually are being updated.
As I said before, sometimes change some packages can be a good way.
All open source / free framework needs someone with a deep knowledge to do advanced things. Newbies upgrading big versions could be a challenge in any framework.
List here what all your packages that are breaking, maybe someone can give you some advices. I got some packages that just need to add the configuration to accept Meteor version 3. It is a very simple change, that you can try quickly.
Try to clean all packages and add them one by one. This help a lot.