With transition to now v. 2.0 there is basically no more option to use it with Meteor. See also the thread on meteor-now
and 2.0:
jkrup commented on 9 Nov 2018
Unfortunately with the current planned direction of Now, you're correct that it indicates MeteorJS will become essentially incompatible with Now.
However, I won't let that be the end to this project. Which will remain the easiest/zero-config way to deploy meteor apps. I've actually have already experimented with deploys on a different platform that starts very cheap (
I'll also try to reach out to some people at Zeit and see if they can help come up with a solution as well. @timneutkens
https://github.com/jkrup/meteor-now/issues/133
You can also read more in the migration guide: https://zeit.co/docs/v2/platform/upgrade-to-2-0/
Okay so I tried to switch my platform to now 1 but for my account this is already not working anymore. The option is on https://zeit.co/account already disabled:

If you are able to still use platform v.1 you may configure in your package.json
a property "now": { ... }
or add a now.json
and configure your now service there.
If you configure using now.json
you may place it in your project root and also run meteor-now ... --local-config
.