Still trying to meteor update -LESS advice

help
1

I saw this advice:
Best way to support Meteor 1.1 and 1.2 with LESS

api.use('less@1.0.0 || 2.0.0');

Where do I put this?

****I want to update an old app that works in METEOR@1.1.0.3
trying to get it to METEOR@1.2
meteor update --release 1.2 Update to release METEOR@1.2 is impossible:
While selecting package versions:
error: Conflict: Constraint less@1.0.14 is not satisfied by less 2.5.0_1.
Constraints on package “less”:

  • less@=2.5.0_1 <- top level
  • less@2.5.0_1 <- accounts-ui 1.1.6
  • less@2.5.0_1 <- accounts-ui-unstyled 1.1.8 <- accounts-ui 1.1.6
  • less@1.0.14 <- matb33:bootstrap-tooltip 3.3.4
  • less@1.0.14 <- matb33:bootstrap-base 3.3.4 <- matb33:bootstrap-tooltip 3.3.4
  • less@1.0.11 <- yogiben:autoform-modals 0.3.6
2

First thing I would try is running the update with the --all-incompatible-update flag and see if that satisfies the constraint resolver

3

Thank heaps, I’m not sure I’m got that flag?
I see this:

meteor update --release 1.2 --all-incompatible-update
–all-incompatible-update: unknown option.
Usage: meteor update
meteor update --patch
meteor update --release
meteor update --packages-only
meteor update [packageName packageName2 …]

4

Sorry, I was on mobile and autocorrect apparently got the best of me and I didn’t notice… The flag is --allow-incompatible-update

5

Much appreciated,
The Less errors seem to block the update.
I am no expert on Less …added by other packages.
Is there anything else that might allow an update?

Thankyou !

meteor update --release 1.2   --allow-incompatible-update               Update to release METEOR@1.2 is impossible:
While selecting package versions:
error: Conflict: Constraint less@1.0.14 is not satisfied by less 2.5.0_1.
Constraints on package "less":
* less@=2.5.0_1 <- top level
* less@2.5.0_1 <- accounts-ui 1.1.6
* less@2.5.0_1 <- accounts-ui-unstyled 1.1.8 <- accounts-ui 1.1.6
* less@1.0.14 <- matb33:bootstrap-tooltip 3.3.4
* less@1.0.14 <- matb33:bootstrap-base 3.3.4 <- matb33:bootstrap-tooltip 3.3.4
* less@1.0.11 <- yogiben:autoform-modals 0.3.6
6

Yes, with the caveat that things may not work completely as expected due to not respecting the semver contract :man_shrugging:. That being said, I’d make sure you’ve commited and branched so that you can easily get back to the working state and then edit .meteor/packges and add/modify the line for less to be less@2.5.0_1!

7

I don’t think this will work with release 1.2?
IIRC it was introduced around 1.7 or 1.8?

EDIT: History.md shows it was added in 1.8

8

Oh no! I didn’t realize that…

9

Thanks for answering guys,
Ive git checked it out to the working version.
I then runs …it all works great.

I searched all files for any mention of 2.5.0_1 in any strings
there are none. I rechecked this in Ultrafile search as well as VSCode in case.

I still get this result below, what action does this suggest?
Thankyou, I need to try to update app.

meteor update --release 1.2   --allow-incompatible-update
Update to release METEOR@1.2 is impossible:
While selecting package versions:
error: Conflict: Constraint less@1.0.14 is not satisfied by less 2.5.0_1.
Constraints on package "less":
* less@=2.5.0_1 <- top level
* less@2.5.0_1 <- accounts-ui 1.1.6
* less@2.5.0_1 <- accounts-ui-unstyled 1.1.8 <- accounts-ui 1.1.6
* less@1.0.14 <- matb33:bootstrap-tooltip 3.3.4
* less@1.0.14 <- matb33:bootstrap-base 3.3.4 <- matb33:bootstrap-tooltip 3.3.4
10

Unfortunately you’re options are limited to either trying to get the author to update the packages, fork them and submit pull requests and hope they accept them, or just clone them into your packages dir and edit the source so that the constraint resolver is satisfied. There of course may be other updates necessary depending on what changed from 1.0.14 to 2.5.0_1

11

Thanks very much,
This is tough, I have no clue about Less
Might the below be plugged in somewhere?

Best way to support Meteor 1.1 and 1.2 with LESS

api.use('less@1.0.0 || 2.0.0');

Cheers

12

Yes, once you’ve cloned the offending packages into your project’s packages directory, you can then edit their package.js file to contain this line. The specification of both versions serves very little purpose in this case though since you won’t likely be releasing it for use by others where this might be useful. Therefore you can safely just specify a single version.

1 Like
13

Thanks heaps copleykj
I removed matb33:bootstrap-tooltip (and the minor feature it supported)
and removed yogiben:autoform-modals@0.3.6 (unused)

Then the standard update process to 1.2 worked

Appreciate your kind assistance

14

@markpdev no problem, glad you got things sorted out.