Alanning:roles v3 released

announce
22

Need help with this error… using “alanning:roles@4.0.0-alpha.4”

> Package['alanning:roles'].Roles._forwardMigrate2()
Uncaught TypeError: Package.alanning:roles.Roles._forwardMigrate2 is not a function
    at REPL45:1:33
    at ContextifyScript.runInThisContext (node:vm:136:12)
    at defaultEval (node:repl:598:22)
    at bound (node:domain:432:15)
    at runBound (node:domain:443:12)
23

There was no need to do a migration step from V3 to V4. Data structure seems to be the same, only thing changed is that everything is async on the server siede now. If you come from V2 you might have to go through V3 before V4 maybe?

24

The migrations functions were removed in the v4 upgrade.

25

I’m getting a weird error. I was using alanning:roles@3.4.0 with Meteor 2.16 perfectly fine. However, I when upgraded to Meteor 3.0.1, it was downgraded to alanning:roles@1.2.10 which in turn is incompatible with Meteor 0.9.0 or later. Then I tried running meteor add alanning:roles@3.6.3, but then I get an error saying that v3.6.3 is incompatible with several Meteor 3 core packages, including accounts-base 3.0.0, mongo 2.0.0, and blaze 3.0.0. WTH?

Edit: I solved it by removing the existing version of alanning:roles in my app and adding it again by pinning it to 4.0.0-alpha.4

26

@belfigue yes, that is the current solution. I’m planning to more to roles official v4 release soon.