Looking for solutions for the constraints that hold me back to update to Meteor 3.0.2

help
1

I’ve updated all packages that can be updated but now I’m stuck with the following list of constraints when I tried to upgrade to Meteor 3.0.2:

meteor update

=> Errors while initializing project:

While selecting package versions:

error: Conflict: Constraint blaze@2.8.0 is not satisfied by blaze 3.0.0.

Constraints on package "blaze":

* blaze@2.8.0 <- blaze-html-templates 2.0.1

* blaze@3.0.0 <- spacebars 2.0.0 <- harry97:ssr 2.2.2

* blaze@3.0.0 <- templating-runtime 2.0.0 <- templating 1.4.4 <- blaze-html-templates 2.0.1

* blaze@2.7.1 || 2.8.0 || 2.9.0 || 3.0.0-alpha300.0 <- ostrio:flow-router-extra 3.11.0-rc300.1

* blaze@3.0.0 <- accounts-base 3.0.1 <- accounts-password 3.0.1

* blaze@3.0.0-alpha300.17 <- harry97:ssr 2.2.2

* blaze@2.5.0||3.0.0-alpha300.17 <- useraccounts:core 1.17.1

Conflict: Constraint webapp@1.3.10 is not satisfied by webapp 2.0.1.

Constraints on package "webapp":

* webapp@2.0.1 <- top level

* webapp@~2.0.1 <- top level

* webapp@2.0.0 <- meteor-base 1.5.2

* webapp@2.0.0 <- routepolicy 1.1.2 <- ddp-server 3.0.1 <- ddp 1.4.2 <- accounts-base 3.0.1 <- accounts-password 3.0.1

* webapp@2.0.0 <- routepolicy 1.1.2 <- ddp-server 3.0.1 <- ddp 1.4.2 <- accounts-password 3.0.1

* webapp@2.0.0 <- routepolicy 1.1.2 <- meteorhacks:inject-initial 1.0.3 <- utilities:avatar 0.9.2

* webapp@2.0.0 <- routepolicy 1.1.2 <- webapp 2.0.1

* webapp@2.0.1 <- ddp-server 3.0.1 <- ddp 1.4.2 <- accounts-base 3.0.1 <- accounts-password 3.0.1

* webapp@2.0.1 <- ddp-server 3.0.1 <- ddp 1.4.2 <- accounts-password 3.0.1

* webapp@2.0.0 <- autoupdate 2.0.0 <- hot-code-push 1.0.5 <- meteor-base 1.5.2

* webapp@2.0.1 <- mongo 2.0.1

* webapp@1.3.10 <- nitrolabs:cdn 1.3.0

* webapp@2.0.0 <- browser-policy-content 2.0.0 <- browser-policy 1.1.3

* webapp@2.0.0 <- browser-policy-common 1.0.13 <- browser-policy 1.1.3

* webapp@2.0.0-rc300.8 <- montiapm:agent 3.0.0-beta.5

Conflict: Constraint typescript@3.7.0 || 4.1.2 || 4.3.2 || 4.9.5-beta300.0 is not satisfied by typescript 5.4.3.

Constraints on package "typescript":

* typescript@~5.4.3 <- top level

* typescript@5.4.3 <- logging 1.3.5 <- email 3.0.100

* typescript@4.9.5 || 5.4.3-rc300.0 <- ostrio:flow-router-extra 3.11.0-rc300.1

* typescript@3.7.0 || 4.1.2 || 4.3.2 || 4.9.5-beta300.0 <- itgenio:persistent-session 0.4.12

Conflict: Constraint jquery@3.0.0 is not satisfied by jquery 1.11.11.

Constraints on package "jquery":

* jquery@1.11.10 <- top level

* jquery@1.11.9 || 3.0.0 <- blaze 3.0.0 <- accounts-base 3.0.1 <- accounts-password 3.0.1

* jquery@1.11.9 || 3.0.0 <- blaze 3.0.0 <- blaze-html-templates 2.0.1

* jquery@1.11.3 <- peppelg:bootstrap-3-modal 1.0.4

* jquery@1.0.0 <- lookback:tooltips 0.3.1

* jquery@1.0.0 <- jeremy:selectize 0.12.1_5

* jquery@1.0.1 <- chrismbeckett:toastr 2.1.2_1

* jquery@3.0.0 <- useraccounts:core 1.17.1

Would appreciate any help to point me in the right direction as to how I can overcome these constraints. Thank you in advance!

2

Alright, let’s brake this down.
Strangely blaze-html-templates is not at the latest version. Try to force it to 3.0.0, but this might be result of another dependency.
ostrio:flow-router-extra needs to release a final version with updated dependency list, but I don’t think that is a problem here. Same with harry97:ssr and useraccounts:core
nitrolabs:cdn is out of date and probably won’t be updated. It was continued by zodern:cdn, but I think that one is not ready for v3 either, mine storyteller:cdn is and I have just published a version that should give no trouble for v3. Please migrate.
itgenio:persistent-session is the hold-up for typescript. Please ask them to include to add TS v5 to the options.
jquery is being held back by peppelg:bootstrap-3-modal, lookback:tooltips, jeremy:selectize, chrismbeckett:toastr. Probably best to fork these locally and fix. @jkuester might have more insight on these things.

If you like my work, please sponsor me or you can schedule a consultation with me.

1 Like
3

I use peppelg:bootstrap-3-modal@1.0.4 in my app in v3 and this is working fine.

In my packages file I have this : jquery@3.0.0! (with exclamation mark)
In my pacakges file I have this : blaze-html-templates@3.0.0-rc300.2 (forced)

I use ostrio:flow-router-extra@3.11.0-rc300.1 in my app v3 and this is working well

(Also using blaze)

montiapm:agent is NOT working in my app in v3, so I had to remove it to make the migration

I was using chrismbeckett:toastr a few years but I have replaced with toastify-js (no meteor package)

4

Followed advises listed here and I’m a bit closer, though not there yet.

I’m currently using:

blaze-html-templates@3.0.0-rc300.2

and

jquery@3.0.0!

as you suggested but I still get the following restriction when I run Meteor update:

meteor update
=> Errors while initializing project:

While selecting package versions:
error: Conflict: Constraint typescript@3.7.0 || 4.1.2 || 4.3.2 || 4.9.5-beta300.0 is not satisfied by typescript 5.4.3.
Constraints on package “typescript”:

  • typescript@~5.4.3 ← top level
  • typescript@5.4.3 ← logging 1.3.5 ← email 3.0.100
  • typescript@4.9.5 || 5.4.3-rc300.0 ← ostrio:flow-router-extra 3.11.0-rc300.1
  • typescript@3.7.0 || 4.1.2 || 4.3.2 || 4.9.5-beta300.0 ← itgenio:persistent-session 0.4.12

The latest versions seems to present a constraint here, right?

Done, see Update package.json - it's otherwise a constraint for upgrading to Meteor 3.x by a4xrbj1 · Pull Request #2 · itgenio/meteor-persistent-session · GitHub

It’s also held back by email 3.0.100 and ostrio:flow-router-extra 3.11.0-rc300.1.

Any further recommendations?

5

For the persistent-session, you don’t really care about package.json, you care here more about what is in package.js:

1 Like
6

Thanks Jan for that 2nd CR. However, it seems that no one is maintaining this package anymore or am I wrong?

Screenshot 2024-09-27 at 17.19.03
Screenshot 2024-09-27 at 17.19.03770×476 35.4 KB

7

0 members means 0 public members. You will have to reach out to the company or some of the people who have maintained that package in the past.

8

They actually merged a PR for me @afrokick

1 Like
9

Hiya, I’m trying to upgrade from Meteor METEOR@2.14 to Meteor 3 and I’m seeing similar problems but they seem to be in the core Meteor packages?

This is what I’m running:

meteor update --release 3.1

I’ve removed ALL manually added packages, so my package file contains only this:

meteor-base@1.5.1 # Packages every Meteor app needs to have
mobile-experience@1.1.1 # Packages for a great mobile UX
mongo@1.16.8 # The database Meteor supports right now
blaze-html-templates@1.0.4 # Compile .html files into Meteor Blaze views
tracker@1.3.3 # Meteor’s client-side reactive programming library

standard-minifier-css@1.9.2 # CSS minifier run for production mode
standard-minifier-js@2.8.1 # JS minifier run for production mode
es5-shim@4.8.0 # ECMAScript 5 compatibility for older browsers
ecmascript@0.16.8 # Enable ECMAScript2015+ syntax in app code
shell-server@0.5.0 # Server-side component of the meteor shell command

The error I get is:

=> Errors while initializing project:

While selecting package versions:
error: Conflict: Constraint blaze@3.0.0-rc300.2 is not satisfied by blaze 2.7.1.
Constraints on package “blaze”:

  • blaze@3.0.0-rc300.2 ← launch-screen 2.0.1 ← mobile-experience 1.1.2
  • blaze@2.5.0 ← blaze-html-templates 1.2.1
  • blaze@2.3.2 ← ui 1.0.13 ← blaze-html-templates 1.2.1
  • blaze@2.5.0 ← spacebars 1.3.0 ← blaze-html-templates 1.2.1

Conflict: Constraint templating@1.4.4-rc300.2 is not satisfied by templating 1.0.3.
Constraints on package “templating”:

  • templating@1.4.4-rc300.2 ← launch-screen 2.0.1 ← mobile-experience 1.1.2
  • templating@1.4.1 ← blaze-html-templates 1.2.1

Conflict: Constraint templating@1.4.1 is not satisfied by templating 1.0.3.
Constraints on package “templating”:

  • templating@1.4.4-rc300.2 ← launch-screen 2.0.1 ← mobile-experience 1.1.2
  • templating@1.4.1 ← blaze-html-templates 1.2.1

Can any one suggest what I can try to fix this?

10

It seems that all your incompatibilities come from blaze-html-templates. You seem to have version 1.2.1 while the most recent version is 3.0.0
https://packosphere.com/meteor/blaze-html-templates

11

Thanks yes, I saw that but as it’s part of the main Meteor infrastructure, I assume it is managed by the Meteor upgrade process - I didn’t add it manually, so didn’t expect to upgrade it manually?

12

Thanks, the upgrade to Meteor 3.1 runs after I ran this:

meteor add blaze-html-templates

I won’t know if it’s really successful until I manage to get all my packages either upgraded or replaced, but it’s a step forward!