[FIXED] Problem upgrading to 2.3.2

core
1

Hi,

2.2.1 worked fine but it seems a package is not compatible with 2.3.2 (or the newer Node version!).

Blockquote
W20210714-11:30:42.635(-4)? (STDERR) /Users/user/.meteor/packages/meteor-tool/.2.3.2.d8p0d1.8tnqq++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:280
W20210714-11:30:42.699(-4)? (STDERR) throw(ex);
W20210714-11:30:42.699(-4)? (STDERR) ^
W20210714-11:30:42.699(-4)? (STDERR)
W20210714-11:30:42.699(-4)? (STDERR) TypeError: Cannot read property ‘_handleConnect’ of undefined
W20210714-11:30:42.699(-4)? (STDERR) at exposeLivedata (packages/lamhieu_meteorx.js:26:25)
W20210714-11:30:42.700(-4)? (STDERR) at packages/lamhieu_meteorx.js:200:1
W20210714-11:30:42.700(-4)? (STDERR) at packages/lamhieu_meteorx.js:225:4
W20210714-11:30:42.700(-4)? (STDERR) at packages/lamhieu_meteorx.js:233:3

We have no direct dependency on lahmieu_meteorx.js and when we uninstall it, meteor reinstalls it automatically when building.

1-How can we find which other package depend on the broken one?
2-Has anybody experienced this problem when upgrading to 2.3.2 ?

Best regards,

Burni

2

lamhieu:meteorx is not compatible with Meteor 2.3, most likely some APM package depends on it.

You can use meteor list --tree to see the dependencies of your packages.

3

Hi,

thanks a lot!
That helped me find the culprit.

It was that old version of montiapm:agent@2.29.0 I was using. updating it changed the dependencies to montiapm:meteorx so I’m assuming the developer forked/fixed the meteorx package.

Thanks a lot for your help!!

Regads,

Burni

1 Like
4

Yes, montiapm is up to date.

1 Like