Meteor.js 3.0 is an upcoming major release with lots of breaking changes. The platform is moving away from Fibers to use Node's native async await ...
For further actions, you may consider blocking this person and/or reporting abuse
For the
count
, the migration should be more advanced, from documentation:Thanks for the hint, I will update this one
Trying to use the ValidationMethod override, but stomped with this error... not sure if the "analyze" method requires another import?
Thanks!
Did you use the
jkuester:migration-helper
package or did you used the code from this article?Hi! Both... here's the snippet. Puzzled because I read the code and figure out a couple of imports might be required... but the helper still outputs to the console that my method is not async yet.
And this is the method code (very simple case):
Any advice will be appreciated... working hard on refactoring my webapp to migrate to v3 ASAP.
Cheers
Thanks for the examples I will try to reproduce this. In the meantime, there has also been an eslint-plugin being developed by quave, which can also help you to detect parts that need migration (it is specifically designed for this task):
github.com/quavedev/eslint-plugin
Will get back to you when I find the cause for the issue.
Thank you!
Also, wanted to pick someone's brain around how to fix these issues... must I find new packages for these? (debugging results from the suggested migration helper package):
Another one:
Is there a pagination package you'd recommend to use for Meteor 3?
I am using this one but it's not been maintained and JKuster's migration helper reports the underlying methods not being async.
github.com/Kurounin/Pagination/tre...
I believe this library was causing me trouble as it trips the migration helper... as soon as I removed it, all my methods stopped reporting not being async.
mdg:meteor-apm-agent
@jankapunkt FYI