Meteor 3.0-rc.0 is out!

denyhs · April 19, 2024, 9:15pm

We have a new release: `meteor 3.0-rc.0`

We have been working hard to finish this release for Meteor 3, and it’s finally here, our first Release Candidate!

Here are the things we brought:

Fix issue with audit-argument-checks after changes on env contexts [nachocodoner] [PR]
Fix promise rejection throwing several times [nachocodoner] [PR]
Support Linux ARM with the Meteor installer [nachocodoner] [PR]
Sequential packages loading order [radekmie] [PR]
Update apollo skeleton to use async [StorytellerCZ] [PR]

How to test it?

Existing projects:

meteor update --release 3.0-rc.0

meteor reset #Resets local DB and project to a fresh state

Starting a project:

meteor create app-name --release 3.0-rc.0

Your help testing this version by creating a new app or migrating your current one will be extremely helpful!

Please give us your feedback, and if you find any issues, you can create a post here or open an issue on GitHub.

schlaegerz · April 19, 2024, 9:37pm

Getting an error when after updating to version 3 from beta.7

                        
I20240419-14:12:38.287(-7)? error on boot.js TypeError: next.runImage.call is not a function
I20240419-14:12:38.306(-7)?     at processNext (packages/core-runtime.js:127:30)
I20240419-14:12:38.306(-7)?     at Object.queue (packages/core-runtime.js:111:3)
I20240419-14:12:38.306(-7)?     at packages/meteor-base.js:1:47
I20240419-14:12:38.306(-7)?     at /tools/static-assets/server/boot.js:432:36
I20240419-14:12:38.307(-7)?     at /tools/static-assets/server/boot.js:503:13
I20240419-14:12:38.307(-7)?     at AsyncLocalStorage.run (node:async_hooks:346:14)
I20240419-14:12:38.307(-7)?     at /tools/static-assets/server/boot.js:502:37
I20240419-14:12:38.307(-7)?     at Function.run (.meteor/local/build/programs/server/tools/tool-env/profile.ts:315:14)
I20240419-14:12:38.307(-7)?     at startServerProcess (/tools/static-assets/server/boot.js:501:17)
I20240419-14:12:38.307(-7)?     at Object.<anonymous> (/tools/static-assets/server/boot.js:508:2)
I20240419-14:12:38.308(-7)? TypeError: next.runImage.call is not a function
I20240419-14:12:38.308(-7)?     at processNext (packages/core-runtime.js:127:30)
I20240419-14:12:38.308(-7)?     at Object.queue (packages/core-runtime.js:111:3)
I20240419-14:12:38.308(-7)?     at packages/meteor-base.js:1:47
I20240419-14:12:38.308(-7)?     at /tools/static-assets/server/boot.js:432:36
I20240419-14:12:38.308(-7)?     at /tools/static-assets/server/boot.js:503:13
I20240419-14:12:38.308(-7)?     at AsyncLocalStorage.run (node:async_hooks:346:14)
I20240419-14:12:38.308(-7)?     at /tools/static-assets/server/boot.js:502:37
I20240419-14:12:38.309(-7)?     at Function.run (.meteor/local/build/programs/server/tools/tool-env/profile.ts:315:14)
I20240419-14:12:38.309(-7)?     at startServerProcess (/tools/static-assets/server/boot.js:501:17)
I20240419-14:12:38.309(-7)?     at Object.<anonymous> (/tools/static-assets/server/boot.js:508:2)

denyhs · April 19, 2024, 9:38pm

Run a meteor reset and try again. This should fix it!

schlaegerz · April 19, 2024, 9:56pm

Ok thanks! For people like me who don’t like to do meteor reset because I have stuff in my local db

It just needs rm -rf .meteor/local/bundler-cache

fredmaiaarantes · April 20, 2024, 2:52am

nachocodoner · April 22, 2024, 3:29pm

Is it rm -rf .meteor/local/bundler-cache, right?

fredmaiaarantes · April 22, 2024, 3:43pm

schlaegerz · April 22, 2024, 3:49pm

You are right, fixed in my message to not confuse people

rmsbht · April 24, 2024, 5:21am

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.

paulishca · April 24, 2024, 6:38am

did you do this: Meteor 3.0-rc.0 is out! - #6 by nachocodoner

or a meteor reset?

harry73 · April 24, 2024, 1:01pm

Hi,

I have the same and I did a meteor reset before.

On beta7, all was OK.

nachocodoner · April 24, 2024, 1:46pm

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

harry73 · April 24, 2024, 2:19pm

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)

denyhs · April 24, 2024, 2:52pm

Could you create a reproduction of this?

harry73 · April 24, 2024, 5:31pm

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

vikr00001 · April 24, 2024, 8:47pm

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

vikr00001 · April 24, 2024, 9:06pm

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.

vikr00001 · April 25, 2024, 12:32am

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

rjdavid · April 25, 2024, 4:05am

The issue from the error message:

denyhs · April 25, 2024, 2:30pm

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.

Meteor 3.0-rc.0 is out!

We have a new release: meteor 3.0-rc.0

How to test it?

Existing projects:

Starting a project:

We have a new release: `meteor 3.0-rc.0`