Please if could you provide the steps you use to achieve it so. thanksRead full topic

Thanks a lot for taking a look at the profile! I’m currently writing a stress test that connects via ddp and simulates pub/sub from our users. I plan to do comparisons on both Meteor 2 and 3 in production on isolated containers and try to find any clues as to what’s happenning.Read full topic

We’ve reviewed your CPU profile, but it’s difficult to conclude without more context or access to your system’s state. From the information provided, we noticed high garbage collector usage despite sufficient RAM, and some compression occurring within the web app middleware. However, when we compared code from versions 2 and 3, there was no clear difference, apart from using express now instead of connect. Other action is to lowering compression levels could potentially speed up the process. But again, without solid evidence, we don’t want to take any action.We understand that comparing CPU profiles from Meteor 2 and 3 can be hard due to different behaviors at the time of capture. However, if you can obtain multiple profiles from both versions under similar conditions, it might reveal significant differences for further analysis.It would be great you can share these profiles among other info we will ask you about your environment, node heap configs state between Meteor versions, and so

Hard to say for sure. I was able to capture a CPU trace using monti APM, but I can’t pinpoint to anything in particular. The only wierd things in this trace are:out of 10 captured seconds, 700ms are spent in cookie parsing.a lot of time is spent on garbage collection, even though the container was using 1.5GB out of 4 available in containerCan you take a look at the trace and maybe give some insights? https://app-us.montiapm.com/cpf/EsMsKqYti3cgftK6QRead full topic

Sorry to hear that, can you provide more information that might lead to what specifically is causing it? Me or @nachocodoner will reach out to you to help understand it better.Read full topic

Anyone experiencing performance problems after upgrading to Meteor 3? Our CPU usage doubled when we deployed and we were forced to revert.Read full topic

I’m not sure under what circumstances this issue arises. Does it occur in dev mode, when loading locally after meteor build, or when deploying to iOS production?I tested on my end and found that using Meteor.settings or the settings.json file works for both the skeleton and simpletasks projects, in dev mode.I suggest removing added native plugins and meteor packages and code related from your project incrementally, running the app continuously until it stops crashing. Then, try to replicate the issue in a small, reproducible example that we can examine. Since other developers aren’t encountering this issue in iOS, it seems specific to your setup. We need more information to find the proper solution.Read full topic

janmp:What’s the status of Cordova? Getting in to run on iOS used to work without any configuration (well except for the certificate in Xcode). Have not got it to work with Meteor 3 yet.Hi, without any further checking, just a quick info: I built our app on Meteor 3.0 + iOS last week, and it probably hat its settings or nothing would have worked.We’re using an explicit --mobile-settings ./mobile-settings-live.json for the build though.Also another settings package to be able to have default settings (ogourment:[email protected])I just wanted to throw that out.Read full topic

Meteor.settings is not defined on iOS builds. That’s what was causing the problems. Just a white screen with no error message of any kind. Took me a hole day to figure out. Problem also happens when you actually have a settings file. Meteor.settings seems completely broken on iosRead full topic

I have tried running a fresh meteor create app on iOS and that’s working. Figuring, what’s wrong with my actual app is pretty hard, because I do not get any error logs from the cordova app. I don’t get any console.logs from the app at all. The problem must manifest before meteor startup.Found another problem with Safari on iOS and dynamic imports when connecting to the dev server.Read full topic

Cordova works well in Meteor 3.0 for Android and iOS projects. I tested it on both Meteor basic skeletons and the simpletasks app.Did these problems occur in any existing Meteor 2.x project during the transition to Meteor 3.x?If so, it might be an issue with your specific configuration, setup, plugins, or package incompatibilities with latest Node somehow, since nothing around Cordova deps was changed on Meteor 3.x. The new Node.js version used for compilation could cause different building of native dependencies, requiring adjustments.Whether it’s a new app or a migration, please point me to the GitHub issue where you describe the problem and the reproducible steps so we can assist you.Read full topic

I’d like to know for Meteor-Desktop as well. We’re many full versions behind due to the existing limitation of NodeJS on Meteor 2.x - will you be working on migrating it to 3.x and pushing all dependencies @storyteller ?Read full topic

What’s the status of Cordova? Getting in to run on iOS used to work without any configuration (well except for the certificate in Xcode). Have not got it to work with Meteor 3 yet.Read full topic

Congrats to the team and community.It was a huge undertaking and really inspiring to see.Read full topic

Kudos to whole Meteor Team!! Wonderful work and been waiting for this. Congrats!!Read full topic

Since I understood what Meteor is about, almost 5 years ago, I’ve been looking towards the future, towards this day.I’ve grown and learned thanks to Meteor and the projects and businesses it made possible, and somehow destiny brought me ever closer to it.This is the tipping point, as some of you say, the stars are aligning once more.Meteor has faced many challenges in the past: technical, business, and whatever it may be.But it has endured and survived thanks to the ones who embraced it and stuck with it through thick and thin.To those you have my admiration and respect.Let’s build something amazing together.To those arriving or coming back, now is your chance of making an impact, build a product or contribute to the project and ecosystem.Read full topic

denyhs:I’ve been part of this process from start to endYour role was crucial to the project’s success.Thanks for your resilience Read full topic

Since Monday, I’ve been solving some things for the release, so I didn’t take time to post anything here besides a GIF I’ve been part of this process from start to end, literally. It was a crazy ride and a pretty tiring one. And there were some moments I needed to take a step back to breathe. Otherwise, I couldn’t continue. But I continued because I had full support from the community and, especially, from the core team, which always understood how massive this project was and how much it could take from someone.So, I want to thank you all for your hard work and help over those two (three?) years.It’s really amazing to see what we accomplished together as a community.The work isn’t done yet, but now Meteor will thrive towards a bright future Read full topic

Incredible – I was able to migrate four Apps to meteor 3 in less than two hours.In a few places, I had forgotten to use the async api callsthe less packe did not work. I have to use [email protected] collection2 did not work, until I added import 'meteor/aldeed:collection2/static';That’s it!Great work Meteor Team PS: We have planned up to two weeks for the migration and this is one of the rare cases where the job was done much faster!Read full topic

Congrats to everyone who helped out.I want to say a big thanks to the community; without the support, testing, pinging, and question-asking, we would not have been able to get through it.Meteor has a great future ahead of it!Read full topic

Awesome! A huge thank you to all who contributed to the effort especially @denyhs, @grubba, and @nachocodoner for all their hard work. And of course @zodern for their key contributions and guidance.Meteor has a wonderful future ahead!Read full topic

This is a huge milestone and just the start of innovations and upgrades that Meteor.js needs. Read full topic

This is a milestone for all dedicated developers who have believed in Meteor from the start, consistently providing solutions and achieving significant accomplishments both individually and collectively, by offering worthy software to companies and users. It is also an opportunity for others to join in and continue improving Meteor.Thank you to all Meteor team and community! Special thanks to technicians @denyhs and @grubba, whose hands-on work and years of commitment and patience have helped shape Meteor into what it is today with Meteor 3.0.Read full topic

Congratulations. I believe migrating to Meteor 3 will be smooth for us Read full topic

Wowzah! Congratulations and thank you to the team and to all contributors. It has been quite the journey!Read full topic