Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
harryadel opened this issue Apr 21, 2024 · 7 comments
Closed
Labels
good first issue Good first issue or something that should is nice to do. Severity:has-workaround
Milestone

Comments

@harryadel
Copy link
Contributor

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
Copy link
Contributor

jamauro commented Apr 21, 2024

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?

@gustawdaniel
Copy link

In my case meteor reset solved this problem.

@harryadel
Copy link
Contributor Author

Yup, that fixed. Thank you guys!

@zodern
Copy link
Member

zodern commented Apr 22, 2024

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:

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

@zodern zodern reopened this Apr 22, 2024
@denihs
Copy link
Contributor

denihs commented Apr 23, 2024

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

@denihs denihs added this to the Release 3.0 milestone Apr 23, 2024
@dallman2
Copy link

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 :)

@denihs
Copy link
Contributor

denihs commented May 6, 2024

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

@denihs denihs closed this as completed May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good first issue or something that should is nice to do. Severity:has-workaround
Projects
None yet
Development

No branches or pull requests

7 participants