Is it rm -rf .meteor/local/bundler-cache, right?
You are right, fixed in my message to not confuse people
1 Like
Hi I updated meteor to meteor-3-0-rc-0. Its not working there is issues. Previous version was METEOR@3.0-beta.6 which was running fine. As soon as I updated to meteor 3.0-rc.0 there is problem. Any help to fix issues will be appreciated.
Hi,
I have the same and I did a meteor reset before.
On beta7, all was OK.
meteor reset should be enough, unless you don’t want to lose your mongodb data from the local meteor setup, then rm -rf .meteor/local/bundler-cache is appropiate.
However, I like to outline here that we are aware on a solution that would have avoided this annoying issue and to have to reset. We will include on the next RC. Check out this issue: [3.0] error on boot.js TypeError: next.runImage.call is not a function · Issue #13104 · meteor/meteor · GitHub
2 Likes
a meteor reset does not solve the issue.
It seems not to be the same error.
Also, I am using meteor-vite/vite-bundler
W20240424-15:00:42.906(2)? (STDERR) --[Error Stack]----------------------------------------------------------------------
W20240424-15:00:42.906(2)? (STDERR) at parseMeteorPackage (file:///project/node_modules/meteor-vite/dist/bin/worker.mjs:801:11)
W20240424-15:00:42.906(2)? (STDERR) at async _MeteorPackage.parse (file:///project/node_modules/meteor-vite/dist/bin/worker.mjs:1360:35)
W20240424-15:00:42.907(2)? (STDERR) at async Context.load (file:///project/node_modules/meteor-vite/dist/bin/worker.mjs:1778:29)
W20240424-15:00:42.907(2)? (STDERR) at async Object.load (file:///project/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:44323:32)
W20240424-15:00:42.907(2)? (STDERR) at async loadAndTransform (file:///project/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:54954:24)
W20240424-15:00:42.907(2)? (STDERR) at async viteTransformMiddleware (file:///project/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:64430:32)
W20240424-15:02:33.710(2)? (STDERR) 3:02:33 PM [vite] Internal server error:
W20240424-15:02:33.711(2)? (STDERR) ERROR Could not extract name from package in: .meteor/local/build/programs/web.browser/packages/meteor.js
W20240424-15:02:33.711(2)? (STDERR) undefined
W20240424-15:02:33.711(2)? (STDERR)
Could you create a reproduction of this?
You can use this one:
do:
meteor update --release 3.0-rc.0
meteor reset
meteor run
open your browser to http://localhost:3000 and the problem will happen
I’ve got this message. What’s the preferred way to bump all the Meteor packages to the latest versions?
% meteor update --release 3.0-rc.0
=> Errors while initializing project:While selecting package versions:
error: Conflict: Constraint webapp@1.5.0 is not satisfied by webapp 2.0.0-rc300.0.
Constraints on package “webapp”:
- webapp@2.0.0-rc300.0 ← top level
- webapp@~2.0.0-rc300.0 ← top level
- webapp@2.0.0-rc300.0 ← meteor-base 1.5.2-rc300.0
- webapp@2.0.0-rc300.0 ← routepolicy 1.1.2-rc300.0 ← ddp-server 3.0.0-rc300.0 ← ddp 1.4.2-rc300.0 ← accounts-base 3.0.0-rc300.0 ← accounts-2fa 3.0.0-rc300.0
- webapp@2.0.0-rc300.0 ← routepolicy 1.1.2-rc300.0 ← ddp-server 3.0.0-rc300.0 ← ddp 1.4.2-rc300.0 ← accounts-password 3.0.0-rc300.0
- webapp@2.0.0-rc300.0 ← routepolicy 1.1.2-rc300.0 ← oauth 3.0.0-rc300.0 ← oauth2 1.3.3-rc300.0
- webapp@2.0.0-rc300.0 ← routepolicy 1.1.2-rc300.0 ← webapp 2.0.0-rc300.0
- webapp@2.0.0-rc300.0 ← ddp-server 3.0.0-rc300.0 ← ddp 1.4.2-rc300.0 ← accounts-base 3.0.0-rc300.0 ← accounts-2fa 3.0.0-rc300.0
- webapp@2.0.0-rc300.0 ← ddp-server 3.0.0-rc300.0 ← ddp 1.4.2-rc300.0 ← accounts-password 3.0.0-rc300.0
- webapp@2.0.0-rc300.0 ← autoupdate 2.0.0-rc300.0 ← hot-code-push 1.0.5-rc300.0 ← hot-module-replacement 0.5.4-rc300.0
- webapp@2.0.0-rc300.0 ← mongo 2.0.0-rc300.0
- webapp@1.13.0 || 2.0.0-alpha300.19 ← mdg:seo 3.5.1
- webapp@2.0.0-rc300.0 ← oauth 3.0.0-rc300.0 ← oauth2 1.3.3-rc300.0
- webapp@1.5.0 ← staringatlights:inject-data 2.3.0
Update
Aha… meteor update… hmmm… I ran that to update to 3.0-rc.0, but possibly it needs to be run a second time for the packages.
Update #2
After running meteor update for the packages, I’m still getting this message:
% meteor update --release 3.0-rc.0
=> Errors while initializing project:
While selecting package versions:
error: Conflict: Constraint webapp@1.5.0 is not satisfied by webapp 2.0.0-rc300.0.
Constraints on package "webapp":
* webapp@2.0.0-rc300.0 <- top level
* webapp@~2.0.0-rc300.0 <- top level
* webapp@2.0.0-rc300.0 <- meteor-base 1.5.2-rc300.0
* webapp@2.0.0-rc300.0 <- routepolicy 1.1.2-rc300.0 <- ddp-server 3.0.0-rc300.0 <- ddp 1.4.2-rc300.0 <- accounts-base 3.0.0-rc300.0 <- accounts-2fa 3.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- routepolicy 1.1.2-rc300.0 <- ddp-server 3.0.0-rc300.0 <- ddp 1.4.2-rc300.0 <- accounts-password 3.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- routepolicy 1.1.2-rc300.0 <- oauth 3.0.0-rc300.0 <- oauth2 1.3.3-rc300.0
* webapp@2.0.0-rc300.0 <- routepolicy 1.1.2-rc300.0 <- webapp 2.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- ddp-server 3.0.0-rc300.0 <- ddp 1.4.2-rc300.0 <- accounts-base 3.0.0-rc300.0 <- accounts-2fa 3.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- ddp-server 3.0.0-rc300.0 <- ddp 1.4.2-rc300.0 <- accounts-password 3.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- autoupdate 2.0.0-rc300.0 <- hot-code-push 1.0.5-rc300.0 <- hot-module-replacement 0.5.4-rc300.0
* webapp@2.0.0-rc300.0 <- mongo 2.0.0-rc300.0
* webapp@1.13.0 || 2.0.0-alpha300.19 <- mdg:seo 3.5.1
* webapp@2.0.0-rc300.0 <- oauth 3.0.0-rc300.0 <- oauth2 1.3.3-rc300.0
* webapp@1.5.0 <- staringatlights:inject-data 2.3.0
I tried rm -rf .meteor/local/bundler-cache. Is there an easy way to recover your mongo db data after running meteor reset? Otherwise I can do a mongo export / import.
Running meteor reset did not yet resolve the anomaly.
% meteor reset
Project reset.
% meteor update --release 3.0-rc.0
=> Errors while initializing project:
While selecting package versions:
error: Conflict: Constraint webapp@1.5.0 is not satisfied by webapp 2.0.0-rc300.0.
Constraints on package "webapp":
* webapp@2.0.0-rc300.0 <- top level
* webapp@~2.0.0-rc300.0 <- top level
* webapp@2.0.0-rc300.0 <- meteor-base 1.5.2-rc300.0
* webapp@2.0.0-rc300.0 <- routepolicy 1.1.2-rc300.0 <- ddp-server 3.0.0-rc300.0 <- ddp 1.4.2-rc300.0 <- accounts-base 3.0.0-rc300.0 <- accounts-2fa 3.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- routepolicy 1.1.2-rc300.0 <- ddp-server 3.0.0-rc300.0 <- ddp 1.4.2-rc300.0 <- accounts-password 3.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- routepolicy 1.1.2-rc300.0 <- oauth 3.0.0-rc300.0 <- oauth2 1.3.3-rc300.0
* webapp@2.0.0-rc300.0 <- routepolicy 1.1.2-rc300.0 <- webapp 2.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- ddp-server 3.0.0-rc300.0 <- ddp 1.4.2-rc300.0 <- accounts-base 3.0.0-rc300.0 <- accounts-2fa 3.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- ddp-server 3.0.0-rc300.0 <- ddp 1.4.2-rc300.0 <- accounts-password 3.0.0-rc300.0
* webapp@2.0.0-rc300.0 <- autoupdate 2.0.0-rc300.0 <- hot-code-push 1.0.5-rc300.0 <- hot-module-replacement 0.5.4-rc300.0
* webapp@2.0.0-rc300.0 <- mongo 2.0.0-rc300.0
* webapp@1.13.0 || 2.0.0-alpha300.19 <- mdg:seo 3.5.1
* webapp@2.0.0-rc300.0 <- oauth 3.0.0-rc300.0 <- oauth2 1.3.3-rc300.0
* webapp@1.5.0 <- staringatlights:inject-data 2.3.0
The issue from the error message:
This is another error.
* webapp@1.5.0 <- staringatlights:inject-data 2.3.0 means that the package staringatlights:inject-data uses webapp@1.5.0, which conflicts with the version webapp@2.0.0-rc300.0.
The package staringatlights:inject-data needs to be updated to be compatible with version 3.
Ok, thanks! I’ll have a look at this.
Is staringatlights:inject-data something that Meteor requires? It may be something I added a long time ago and forgot about. If so I can probably just delete it.
I have a feeling staringatlights:inject-data is something I added at some point and no longer use. I removed it and Meteor updated successfully. I’ll run the app now and see how it goes. 
Seems like the the new Meteor release release has a slightly different package registration signature from the Beta releases. Just shipped a patch for meteor-vite now to address this.
Updating it should solve the issue for you. 
meteor npm i meteor-vite@latest
5 Likes