Initially brought up in feathersjs-ecosystem/authentication#72, sub-apps will hook into their parent setup (so that you don't have to call a sub-apps setup manually) only when a real-time provider is configured. This should however always be the case.
Since it may cause odd errors (with app.setup being run twice) the best way is probably to change this in v3.
Initially brought up in feathersjs-ecosystem/authentication#72, sub-apps will hook into their parent
setup(so that you don't have to call a sub-appssetupmanually) only when a real-time provider is configured. This should however always be the case.Since it may cause odd errors (with
app.setupbeing run twice) the best way is probably to change this in v3.