Looking for help migrating packages to Meteor 3.0

I’ll be starting to mark packages that don’t need any migration work in blue. The first one is ostrio:cookies. I tried adding it to a fork of simpletasks and it works just fine.


@harry97 it’s maybe best if you put an explicit value in the status column maybe for explicitness (see zen of python: explicit is better than implicit) & sort / filterability. We can still use conditional formatting for colors & bling :slight_smile:

A not so “tiny” update: A new version of Collection2 has been released. You can try it now by updating your package to aldeed:collection2@4.0.0-beta.2 . We’re eagerly awaiting your feedback here

4.0.0-beta.6 is out which supports dynamic & static loading. And I forked meteor-schema-index which is compatible with the latest collection2. Please give it a go guys. This fork should hopefully make the leap to 3.0 a little bit easier.

I think now it’s also worth mentioning that my work on the 3.0 packages is being sponsored by Trusted Care AG/@DanielDornhardt which I wouldn’t have been able to do otherwise. They didn’t ask me to write this :stuck_out_tongue_closed_eyes:. I’m truly grateful to them and how they’re giving back to the community hopefully other companies in the Meteor space can follow suit.


Thank you @harry97 for your good work! At least I hope so, I didn’t check the PR yet! :smiley: But I have faith in you!

Thank you for helping out with the packages migration! Amazing work so far zoomer! :stuck_out_tongue:

1 Like

Another day, another update.


I am writing this comment to try to solve a package migration problem. In this regard, I started a discussion about changing the way packages are loaded, which makes some important libraries unusable for the time being. In my case: redis-oplog, lai:collection-extensions, mongo-collection-instances. In particular, all libraries that for some reason need to overload the collections constructor. The bug is tricky in that it can work in some cases, depending on when the package is loaded.

I would like to know if any of you have encountered this problem and if you have found a solution. Currently this problem makes it impossible to migrate my applications.

We had issues with a couple of monkey patches for Mongo. The patches are related to indexing, so kind of have to be used when the app starts. In our case, putting the code using the patches in Meteor.startup(...) solved the issue. But that’s only one use case.

Perhaps, with lai:collection-extensions, and mongo-collection-instances, consider loading them in a dedicated internal package, let’s call it pbeato:mongo, and export Mongo from it (those packages already load mongo by themselves). Put pbeato:mongo at the top of the packages file, and also import { Mongo } from 'meteor/pbeato:mongo' in whatever package/module you need it.

Cross posting here from Large SaaS migrated to 3.0.

We forked locally and migrated a bunch of packages:

coagmano:stylus #(Only v1, because we need cross-package imports but v2 is also relatively easy)

Some, like aumel:security-authorization, may not be everyone’s cup of tea, and unless the maintainer accepts a pull request, we’ll just keep it as a local fork.

Looking to contribute the changes to reywood:publish-composite, coagmano:stylus, and storyteller:cdn to the respective repositories, because they are still maintained.

However, what is to be done with the rest? Some, like simple:json-routes and useraccounts:* are under Meteor Compat Packages · GitHub, so I’m not sure there is anyone available to merge our pull requests there.

The kadira:* / meteorhaks:* packages - their maintainer is long gone, and these packages have been forked countless times. I am not keen on contributing further to this fragmentation, thus it is preferable that we do not put them under the illustreets namespace. So, I’m looking for ideas here. They are very useful, and like in the case of sikka, uniquely useful. Hopefully Meteor Community · GitHub would like to take at least some of them under their umbrella, and we will continue to maintain them for the foreseeable future.

1 Like

Some good news on this one. Our changes have been merged into this pull request: Update tests by StorytellerCZ · Pull Request #173 · Meteor-Community-Packages/meteor-publish-composite · GitHub. It is awaiting review and hopefully will be published soon.


A package often shunned because of performance issues with large collections (but that is just simply misuse!), otherwise very helpful in a multitude of use cases. We just submitted a pretty big pull request here: Meteor 3.0 compatibility by manueltimita · Pull Request #99 · percolatestudio/publish-counts · GitHub. The repo still looks maintained, so hopefully it will be merged soon.


Another package that seems to be still maintained (@storyteller’s pull request from 2 months ago got merged). We also submitted a pull request there, for compatibility with Meteor 3.0: Compatible with Meteor 3.0 by manueltimita · Pull Request #35 · deanrad/meteor-promise · GitHub


Unfortunately I cannot upgrade activitree:push until we get a buildable version of Meteor 3. Testing requires authorized domains and can only test it in production.
On Cordova side successful mobile builds are also required.

The alternative to activitree:push, as I noticed is using OneSignal or other 3rd parties but they are not GDPR compliant or at least they cannot guarantee confidentiality of messages.

Hopefully Beta.1 or 2 will be deployable to clouds.

This one should have now an update that should be fine with Meteor 3 beta.

Merging there is Meteor Software responsibility, so it should be able to get in.

We do have some of them under MCP. inject-initial sounds very similar to inject-data, we’ll have to look into this.

This is under Percolate Studios, so that is managed by Meteor Software as well.

I maintain montiapm:meteorx, which has been updated for Meteor 3.

1 Like

inject-data only has a subset of functionality found in inject-initial, which is injecting data into the HTML sent to the client.

inject-initial on the other hand gives you access to the raw html, head, and body of the page, before being sent to the client, so one can modify the HTML, inject conditional CSS, scripts, and do all kinds of voodoo.

Here is a stripped down overview of the API:

Inject = {
  // stores in a script type=application/ejson tag, accessed with Injected.obj('id')
  obj: function(id, data, res) {
      'Inject.obj(id, data [,res]) expects `data` to be an Object or Function');
    // ..

  // Inserts a META called `id`, whose `content` can be accessed with Injected.meta()
  meta: function(id, data, res) {
      'Inject.meta(id, data [,res]) expects `data` to be an String or Function');
    // ..

  rawHead: function(id, textOrFunc, res) {
      'Inject.rawHead(id, content [,res]) expects `content` to be an String or Function');

  rawBody: function(id, textOrFunc, res) {
      'Inject.rawBody(id, content [,res]) expects `content` to be an String or Function');
    // ..

  // The callback receives the entire HTML page and must return a modified version
  rawModHtml: function(id, func) {
    // ..

I think you should publish those packages one way or another. I’m most interested in useraccounts:* & kadira:blaze-layout. useraccounts is one of the reasons that made Meteor click for me and it was a joy to spin up application with full blown authentication. How different is your blaze-layout fork to GitHub - trychlos/pwix-blaze-layout: Layout Manager for Blaze (works well with Meteor FlowRouter) ?

I’m glad to hear that you are still using useraccounts:*. I thought I’m the only archaeologist digging up these old packages. I agree, they are pretty capable, and so easy to extend, via config or directly in the code. I will send pull requests for three of them that I forked to the Meteor Compat organisation.

blaze-layout is actually a fork of pwix-blaze-layout, but I prefer to keep it under the kadira namespace, as I assume more users will have that included in their packages. But I could send the pull request to pwix-blaze-layout instead, if that’s what people are using nowadays.

I’m glad to hear that you are still using useraccounts:*. I thought I’m the only archaeologist digging up these old packages. I agree, they are pretty capable, and so easy to extend, via config or directly in the code. I will send pull requests for three of them that I forked to the Meteor Compat organisation.

These packages are what ignited my love for Meteor and I believe they’re also the key to the future. If developers try out these packages they too shall develop the same appetite for Meteor.

Can’t wait to see your pull requests not just for useraccounts:* but for the packages you’ve migrated :+1:

Moar updates

Things are moving pretty fast on the community packages, hopefully all lose ends are tied by the end February as promised.

We’d appreciate if someone can step up and work on Migration 3.0 by klablink · Pull Request #13 · Meteor-Community-Packages/redis-oplog · GitHub
as @storyteller has his hands full now


Hi @storyteller, just a clarification, in the latest release of meteor-collection-hooks it is listed as compatible with Meteor 3 even though the tests do not work, as indicated, and async logic is not implemented, what does it mean to have included in the supported versions 3.0-beta.0?

A quick update from us.
As of now, the following have pull requests submitted:

reywood:publish-composite # Awaiting review from MCP maintainers
tmeasday:publish-counts # Awaiting review from MCP maintainers
deanius:promise # Pull request merged, but current maintainer says it won't publish anymore
useraccounts:core # Pull request sent to Meteor Compat Packages
useraccounts:bootstrap # Pull request sent to Meteor Compat Packages

Update 2:

coagmano:stylus@v1.1.3 # Pull request submitted to MCP
coagmano:stylus@v2.0.3 # Pull request submitted to MCP

Update 3:
(Discussion: Feedback needed: simple:rest compat - #8 by illustreets)

json-routes@v3.0.0 # Pull request submitted to Meteor Compat Packages
rest-json-error-handler@v1.1.3 # Pull request submitted to Meteor Compat Packages

Update 4:

pwix:blaze-layout@v2.3.2 # Pull request submitted to current maintainer