meteor/meteor

[3.0] error on boot.js TypeError: next.runImage.call is not a function

Closed this issue · 7 comments

harryadel commented

Hello, I was trying to update our application to the latest RC and after updating I booted our application to get this error:

Selection_017

jamauro commented

Sounds like the same issue here: https://forums.meteor.com/t/meteor-3-0-rc-0-is-out/61515/2?u=jam

Have you already tried meteor reset or rm -rf .meteor/bundler-cache?

  • 👍1
  • 👀1
gustawdaniel commented

In my case meteor reset solved this problem.

  • 👍1
harryadel commented

Yup, that fixed. Thank you guys!

zodern commented

This should be fixed so meteor reset isn't necessary. The linker cache salt needs to be incremented whenever there are breaking changes in the linker output:

meteor/tools/isobuild/compiler-plugin.js

Line 71 in ba0f42c

const LINKER_CACHE_SALT = 24; // Increment this number to force relinking.

  • 👍8
denihs commented

Nice! We're going to add this to the next rc

  • 👍1
  • ❤️1
dallman2 commented

Thank you for adding this in the next RC. Some of us would rather not clear our local db when doing a meteor version upgrade :)

  • 👍1
denihs commented

This should be fixed now in version 3.0-rc.1