Meteor 1.11 released ๐ŸŽ‰

Woke-up this morning and couldnโ€™t believe my eyes! New Meteor release!

Now a lot has happened since the last release, so here is a quick summary in the community newsletter:

And already work has started on 1.12:


Node.js 12.18.3 Docker image with support for meteor 1.11 is missing๏ผŒLook here, MeteorD - Docker image for MUP, highest version only Node 12.16.1

That is something you want to pester @abernix about.


Where can we find more info on the new hookSend hook for the email package?

Right now I only made public what was before internal hook.
Made a PR to the docs to add a short explanation.
In essence you pass in a function into Email.hookSend which is going to receive object about the email to send. You can do what ever you want and either return true to proceed or false to not send the message.
:thinking: In a future release we should probably add another hook to allow editing the dataโ€ฆ

1 Like

Thatโ€™s awesome thanks!
Editing the content would be nice, but what I wanted to use it for is something simpler.

I donโ€™t want to get stung by my email API costs if something goes wrong with my app.
So this is a useful way to code in a kill switch if something were to break and my app tried to send 10,000 emails an hour overnight or something stupid. Unlikely but a nice feature nevertheless.

Just keep a running total of emails sent since midnight and if it crosses some unrealistic threshold, drop the email and alert me somehow.


Updated to Meteor 1.11 and got these errors

error: Conflict: Constraint email@1.2.3 is not satisfied by email 2.0.0.
Constraints on package "email":

* email@~2.0.0 <- top level
* email@1.2.3 <- kschingiz:meteor-elastic-apm 2.4.0

What is the best way to make an existing package to work with the new email package?

Fork, update the dependency and use from packages folder.


Or, overpower the transient dependency with an exclamation point!


As requested in:
and implemented in


After meteor update from 1.10, my app fails with the following

=> Started proxy.
      throw error;

TypeError [ERR_INVALID_ARG_TYPE] [ERR_INVALID_ARG_TYPE]: The "to" argument must be of type string. Received null
    at validateString (internal/validators.js:120:11)
    at Object.relative (path.js:1054:5)
    at Object.wrapper [as pathRelative] (/Users/robertdickert/.meteor/packages/meteor-tool/.1.11.0.q6y7e2.89d8a++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/tools/static-assets/server/tools/static-assets/server/mini-files.ts:107:14)

we recently removed blaze and are using static-html (with React) - not sure if thereโ€™s something wrong with how we did this, but the app works in 1.10.

In your project, try any of the following:

  1. Delete meteor local cache:
rm -rf .meteor/local
  1. Re-install Meteor
curl | sh

I was having the same ERR_INVALID_ARG_TYPE issue and had to go a few steps further to fix it.

rm -rf node_modules
rm package-lock.json
meteor reset
rm -rf .meteor/local
curl | sh

Yeah i was expecting the updated docker image too. But it wasnt updated and we wanted to deploy to our production server immediatly. So i created my own own docker image out of @abernix 's docker image for updateded meteor and node versions. So you can use it for the time being until he updates his docker.



nice,thank you ver much

1 Like

Clearing caches are for the ERR_INVALIDARG_TYPE errors.

For package version constraints, both the answers of @storyteller and @coagmano above works

@coagmanoโ€™s recommended is a lot easier to implement

1 Like

:tada: this is an awesome release!

Way faster & way less CPU on my machine :slight_smile:

Thanks for all the work!


Thanks. I had to use the same to resolve the issue. I also recently removed blaze and am using static-html (with svelte).

Had to do these further steps as well (after 1.11.1 update) - thanks for sharing!

Iโ€™m also running into this and reinstalling Meteor didnโ€™t seem to help so farโ€ฆ

EDIT: I have another project thatโ€™s been running 1.11.1 fine (I forgot I updated it already) so the error has to be related to something else. Iโ€™ll keep investigating.

1 Like

Ran into this problem too.

Ultimate source of the problem is broken symlinks in the projectโ€™s node_modules/.bin

They donโ€™t seem to bother 1.10, but 1.11 gives the


I simply deleted the broken symlinks and all was well.

1 Like