You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other (e.g. Ionic/Cordova, Node, browser, operating system): N/A
If the release candidate is to support imports like this:
import { AngularFireDatabaseModule, AngularFireDatabase } from 'angularfire2/database';
import { AngularFireAuthModule, AngularFireAuth } from 'angularfire2/auth';
package.json files will be required for the database and auth directories. Otherwise, bundlers that do not use the module entry point in the package.json will not work.
For example, the package.json file that goes into the database directory would have this content:
{ "main": "../bundles/angularfire2.umd.js" }
This is the approach that Angular takes with deep paths. For example, there is a similar package.json file in @angular/core/testing.
Version info
Angular: N/A
Firebase: N/A
AngularFire: Current master
Other (e.g. Ionic/Cordova, Node, browser, operating system): N/A
If the release candidate is to support imports like this:
package.json
files will be required for thedatabase
andauth
directories. Otherwise, bundlers that do not use themodule
entry point in thepackage.json
will not work.For example, the
package.json
file that goes into thedatabase
directory would have this content:This is the approach that Angular takes with deep paths. For example, there is a similar
package.json
file in@angular/core/testing
.There is also more information in this
@ngrx/effects
issue.The text was updated successfully, but these errors were encountered: