We have Meteor (and node 14) running on EB instances that come with Node 18. I don’t think the underlying installed version matters - as Meteor then runs it’s own bundled one.
How are you deploying to production? Did you mean that you are running the meteor tool in production (with the bundled node version)?
We do not run “meteor” nor the “bundled node version” in production. But our custom AMI uses the meteor team’s forked node version. Some folks might be ok with the provided AMI by AWS
We use mup and the EB plugin.
mup will use nvm
to install the version of node required by meteor - so the version bundled with the AMI isn’t important.
AFAIR the problem with deploying Meteor 2.15 on a Node 20 machine in EBS was related to Python and the compilation of/by pre-gyp/node-gyp which I think is used/necessary by bcrypt.
Updates about the first Meteor 3.0 RC Release:
Due to some roadblocks, our ETA for the RC Release has been postponed to 19th April.
These are the tasks for the first RC:
- 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]
- Fix checks [nachocodoner] [PR]
- Sequential packages loading order [radekmie] [PR]
- Update NPM, Node and TypeScript to latest versions [nachocodoner] [PR]
- Update apollo skeleton to use async [StorytellerCZ] [PR]
Estimated Release Dates
- Last Meteor 3.0 Beta: March 26, 2024 -
meteor update --release 3.0-beta.7
- First Meteor 3.0 RC: April 19, 2024
- Meteor 2.16: We plan to start working on a release after the first RC
You can follow the updates on What’s left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.
It is time for a Weekly update
We are proud to say that we have the first Release Candidate for Meteor 3.0
You can check more details about it here.
The priority of the next RC will be to review and fix issues with Cordova’s experience.
Next Releases:
- Meteor 2.16 [PR]
- We plan to release it by the end of this week.
- Meteor 3.0 RC (next): May 3, 2024.
- The plan is to have a new release candidate every 2 weeks.
You can follow the updates on What’s left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.
It is time for a Weekly update
We are proud to say that we have the Release for 2.16 beta
You can check more details about it here .
Tasks and fixes for the next Meteor 3.0 RC:
- Circle CI tests failing for external packages [Group 5]
- Meteor developer accounts do not work when logging in with github · Issue #12418
- Add missing observe async types by StorytellerCZ · Pull Request #13103
- Added
waitUntilAllLoaded
safety check. by radekmie · Pull Request #13102 - refactor(accounts): add ddp type to accounts-client by vit0rr · Pull Request #13042
- Make sure Vue and Svelte apps run with Meteor 3
Next Releases:
- Meteor 2.16 RC [PR]
- We plan to release it early next week, probably Monday (May 6th).
- Meteor 3.0 RC (next): Friday, May 3rd, 2024.
- The plan is to have a new release candidate every 2 weeks.
You can follow the updates on What’s left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.
Can this be included in the next RC candidate?
Yes, it will be included in RC.2!
It is time for a Weekly update
We are proud to say that we have the Release for Meteor 3.0-rc.1
You can check more details about it here.
We also have the Meteor 2.16-rc.0
You can check more details about it here.
Tasks and fixes for the next 3.0 RC:
- Review the Types for WebApp/Express
- [Meteor 3] Fix handling unexpected errors during build by zodern · Pull Request #12675
- Fix and Review any places using findOne in the server
- [Meteor 3] Environment Variables resets value too early · Issue #13112
- [Meteor 3] EnvironmentVariable.withValue has different return value on client and server · Issue #13113
- Unable to create new meteor 3 projects · Issue #13106
- Make sure apollo skeleton works with Meteor 3
- Docs for all modules strict breaking change
- Review security updates
Next Releases:
- Meteor 2.16 - Official [PR]
- We plan to release it next week. Probably until May 14th.
- Meteor 3.0 RC - next [PR]
- Monday, May 20th, 2024.
- The plan is to have a new release candidate every 2 weeks. Every Monday.
- Meteor 3.0 - Official
- We need your help testing the RC versions to make it more stable before the official release.
It is time for a Weekly update
We are proud to say that we have the Release for Meteor 2.16 official
You can check more details about it here.
Next Releases:
- Meteor 3.0 RC - next [PR]
- Monday, May 20th, 2024.
- The plan is to have a new release candidate every 2 weeks. Every Monday.
- Meteor 3.0 - Official
- We need your help testing the RC versions to make it more stable before the official release.
- Meteor 2.X versions
- We plan to hold off on releasing new Meteor 2.X versions for now to focus on the 3.0 releases.
It’s time for a weekly update
It’s been some time, but we are proud to say that we have the Release for Meteor 3.0-rc.2
You can check here for more details.
Tasks and fixes for the next, and final until the official, Meteor 3.0 Release Candidate (rc.3):
- Missing Accounts.addEmailAsync
- Top-level await does not seem to work in Meteor 3
- AllowDeny async compatibility
- Fix WebApp.addRuntimeConfigHook
- Implement reset db option and default without cleaning db
- Upgrade meteor presets packages that are deprecated
- Upgrade Blaze to latest version
- MultiFileCachingCompiler does not set up its internal LRU cache correctly
- Incorrect Node.js version in Meteor 3 projects
- Add doc for vite-bundler in the migration guide
- Review security updates
Meteor 3-rc.3
is expected to arrive on Tuesday, June 11th, stay tuned.
Next Releases
- Meteor 3.0 Official (July 8th, 2024) [PR]
- Meteor 3.0.1 (July 22nd, 2024)
- Meteor 3.0.2 (August 5th, 2024)
These dates are subject to change as we add or remove things from the backlog.
Congrats to Meteor. Finally it’s coming
Can someone confirm this “warning” in the migration document?
TIP
It is not recommended to use concurrent calls. Use
await
for yourMeteor.callAsync
.
Previously, this was only the case if you have stubs. It seems that the “stubs qualifier” is no longer applicable based on the current migration document
You can still use Meteor.call
if you know what you’re doing (not using it with stubs as you mentioned). We recommend that you use Meteor.callAsync
because you won’t need to think about stubs when calling a method, and it will prevent weird behavior.
@denyhs, I am referring to Meteor.callAsync()
in this case. The migration document I linked above mentioned not to use it concurrently.
Then there is this example:
// it is not recommended to use concurrent calls
Promise.all([ // This is not ok
Meteor.callAsync('someMethod'),
Meteor.callAsync('someMethod')
]).then(([data1, data2]) => {
console.log(data1, data2);
});
Yeah, I will review everything in this part of the document. It’s now confusing and seems outdated.
It’s time for a weekly update
We are proud to say that we have the Release for Meteor 3.0-rc.4
You can check here for more details.
Tasks and fixes for the next, and official, Meteor 3.0 Release:
- Ensure the documentation is up to date
- Upgrade Node.js to v20.14
- Improve package version resolution process
- React Router SSR for Meteor 3
- Remove pinned version of packages inside the skeletons
- Add
addEmailAsync
alias - Incorrect Node.js version in Meteor 3 projects
- Review Security Updates
Meteor 3.0 is expected to arrive on Tuesday, July 8th, stay tuned.
Next Releases
- Meteor 3.0.1 (July 22nd, 2024)
- Meteor 3.0.2 (August 5th, 2024)
These dates are subject to change as we add or remove things from the backlog.
I really like the proactive communication form that’s taking place from the Meteor team, showing current and future plans along with past achievements. Please keep them coming
Weekly Update June 28th, 2024
So far we have released rc4
as we mentioned in our previous updates, and work is progressing well for our official Meteor 3 release.
You can check here for more details about our last Release Candidate.
The backlog has evolved a little over the last days with some issues gaining priority, our most important ones are as follows:
- Incorrect Node.js version in Meteor project if the
meteor-tool
is missing, this has gone up in priority but it’s extremely hard to solve, we have a path forward but have some loose ends we need to account for, some tests on Windows are failing at the moment - The method call order when Meteor goes back from offline and authentication
- Finding a replacement for
@vlasky/whomst
since it depends on a package calledposix
which builds a binary and breaks on some installations
We also confirmed that Cordova is working completely fine, this was done by @nachocodoner, one of our developers with the most expertise in that area.
We are also revamping the documentation and researching ways to simplify the mechanics for call
and callAsync
, we have @denyhs at this forefront and also huge help from @zodern . The goal is to make Meteor have the best Developer Experience as possible and the migration as simple as possible too.
Other tasks and fixes for the next, and official, Meteor 3.0 Release:
- Unable to run bundle from “meteor build”
- Ensure the documentation is up to date
- Upgrade Node.js to v20.14
- Improve package version resolution process
- React Router SSR for Meteor 3
- Remove pinned version of packages inside the skeletons
- Add
addEmailAsync
alias - Incorrect Node.js version in Meteor 3 projects
- Review Security Updates
- Rename or remove
asyncLocalStorage
global - Verify
tinytest
major version increase
Meteor 3.0 is expected to arrive on Monday, July 8th or 15th at the most
Next Releases
- Meteor 3.0.1 (July 22nd, 2024)
- Meteor 3.0.2 (August 5th, 2024)
These dates are subject to change as we add or remove things from the backlog.